Triple
T30743446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manion phase |
E782752
|
entity |
| Predicate | temporalVariantOf |
P154137
|
FINISHED |
| Object | Fort Ancient culture |
—
|
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: Fort Ancient culture | Statement: [Manion phase, temporalVariantOf, Fort Ancient culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalVariantOf Context triple: [Manion phase, temporalVariantOf, Fort Ancient culture]
-
A.
isTemporaryVersionOf
Indicates that one entity is a non-final, short-lived or provisional form of another, more permanent entity.
-
B.
isVersionOf
Indicates that one entity is a particular version, edition, or variant derived from another entity.
-
C.
temporal
Indicates a relationship that situates one event, state, or entity in time relative to another (e.g., before, after, or during).
-
D.
likelyVariantOf
Indicates that one entity is probably a variant, version, or alternative form of another entity, based on available evidence or similarity.
-
E.
denotesVariantOf
chosen
Indicates that one entity is a variant or alternative form of another, typically sharing core identity or function with some differences.
- 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_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 8:38 p.m.