Triple
T30744425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Folsom culture |
E782779
|
entity |
| Predicate | hasTypeArtifact |
P40733
|
FINISHED |
| Object | Folsom point |
—
|
NE NERFINISHED |
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: Folsom point | Statement: [Folsom culture, hasTypeArtifact, Folsom point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeArtifact Context triple: [Folsom culture, hasTypeArtifact, Folsom point]
-
A.
hasTypeOfArtifact
chosen
Indicates that one entity is classified as, or belongs to, a particular type or category of artifact in relation to another entity.
-
B.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
C.
hasKeyArtifact
Indicates that an entity possesses or is associated with a crucial or central artifact relevant to a particular context or process.
-
D.
hasPackageType
Indicates that an entity is associated with or classified under a particular type or category of package.
-
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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: April 29, 2026, 8:38 p.m.