Triple
T30163602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stele of the Vultures |
E766733
|
entity |
| Predicate | discoveryDateApproximate |
P139680
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Stele of the Vultures, discoveryDateApproximate, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryDateApproximate Context triple: [Stele of the Vultures, discoveryDateApproximate, late 19th century]
-
A.
discoveryDate
Indicates the date on which something was first discovered or identified.
-
B.
discoveryYear_approx
chosen
Indicates that the year associated with a discovery is known only approximately rather than as an exact calendar year.
-
C.
ageWhenDiscovered
Indicates the age of an entity at the time it was first discovered.
-
D.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
E.
discoveryYear
Indicates the calendar year in which something was first discovered or identified.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 29, 2026, 7:22 p.m.