Triple
T28248852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dog Star |
E712260
|
entity |
| Predicate | observedSinceAntiquity |
P69245
|
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: [Dog Star, observedSinceAntiquity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observedSinceAntiquity Context triple: [Dog Star, observedSinceAntiquity, true]
-
A.
observedInMillennium
Indicates that an entity was observed or occurred during a specified millennium.
-
B.
eraOfSignificance
Indicates the historical period or timeframe during which an entity was particularly important, influential, or noteworthy.
-
C.
discoveredInAntiquity
chosen
Indicates that something was found, identified, or recognized during ancient historical times rather than in the modern era.
-
D.
isAncient
Indicates that the entity existed or originated in a very distant past, typically far earlier than the commonly referenced historical period.
-
E.
dstObservedHistorically
Indicates that something has been observed or recorded at a particular destination or location in the past.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 11:03 p.m.