Triple
T30194161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ur |
E767575
|
entity |
| Predicate | hasFamousFind |
P59857
|
FINISHED |
| Object | Standard of Ur |
—
|
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: Standard of Ur | Statement: [Ur, hasFamousFind, Standard of Ur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamousFind Context triple: [Ur, hasFamousFind, Standard of Ur]
-
A.
hasFamousPass
Indicates that an entity possesses or is associated with a well-known or historically significant pass (such as a route, corridor, or access point).
-
B.
hasFamousSignal
Indicates that an entity is associated with a well-known or widely recognized signal, message, or indicator.
-
C.
hasFamousSection
Indicates that an entity includes or contains a part, area, or segment that is widely recognized or renowned.
-
D.
hasNotableMine
Indicates that an entity possesses or is associated with a mine considered significant or noteworthy in some context.
-
E.
hasFamousArtwork
chosen
Indicates that an entity possesses or is associated with a well-known or widely recognized artwork.
- 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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 29, 2026, 7:29 p.m.