Triple
T32779854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zbruch Idol |
E838322
|
entity |
| Predicate | discoveredInCountryAtTime |
P16041
|
FINISHED |
| Object | Austrian Empire |
—
|
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: Austrian Empire | Statement: [Zbruch Idol, discoveredInCountryAtTime, Austrian Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredInCountryAtTime Context triple: [Zbruch Idol, discoveredInCountryAtTime, Austrian Empire]
-
A.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
B.
wasDiscoveredIn
Indicates that an entity became known or was first identified during a specific time period or at a particular place.
-
C.
discoveryDate
Indicates the date on which something was first discovered or identified.
-
D.
discoveredInCountry
chosen
Indicates that something was discovered within the geographical boundaries or jurisdiction of a specified country.
-
E.
firstAppearedOnGlobeBy
Indicates that an entity made its first appearance or was first featured on a globe created or authored by the specified source.
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 1, 2026, 1:14 a.m.