Triple
T22551275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chûn Quoit |
E557561
|
entity |
| Predicate | isPrehistoric |
P64431
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Chûn Quoit, isPrehistoric, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrehistoric Context triple: [Chûn Quoit, isPrehistoric, true]
-
A.
isAncient
chosen
Indicates that the entity existed or originated in a very distant past, typically far earlier than the commonly referenced historical period.
-
B.
historicPresence
Indicates that an entity existed, was active, or had a notable presence in a particular place or context during a past time period.
-
C.
preEvolution
Indicates that one entity represents an earlier evolutionary form or stage that precedes the evolution into another entity.
-
D.
locatedInGeologicPast
Indicates that something existed or occurred in a specific place during a past geologic time period.
-
E.
earliestKnownAncestor
Indicates that one entity is the most distant (oldest) known ancestor in the lineage of another entity.
- 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_69e11e59db848190b4272ecd2b690ffd |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f7647208190a1aaebd083bf095a |
completed | April 29, 2026, 1:31 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:52 p.m.