Triple
T24846275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Page-Ladson site |
E621753
|
entity |
| Predicate | hasTypeOfArtifacts |
P157618
|
FINISHED |
| Object | bifacial stone tools |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: bifacial stone tools | Statement: [Page-Ladson site, hasTypeOfArtifacts, bifacial stone tools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfArtifacts Context triple: [Page-Ladson site, hasTypeOfArtifacts, bifacial stone tools]
-
A.
hasTypeOfArtifact
Indicates that one entity is classified as, or belongs to, a particular type or category of artifact in relation to another entity.
-
B.
artifactTypeFound
chosen
Indicates that a specific type of artifact has been discovered or identified in association with a given context or location.
-
C.
hasCeramicsType
Indicates that an entity is associated with or classified by a specific type or category of ceramics.
-
D.
hasArchType
Indicates that one entity possesses or is characterized by a particular architectural type or style.
-
E.
hasCharacteristicArtifact
Indicates that an entity is associated with a specific artifact that characterizes, exemplifies, or is typical of it.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 18, 2026, 5:19 a.m.