Triple
T35045845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moorilla Estate |
E1011191
|
entity |
| Predicate | sameSiteAs |
P182045
|
FINISHED |
| Object | Museum of Old and New Art |
—
|
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: Museum of Old and New Art | Statement: [Moorilla Estate, sameSiteAs, Museum of Old and New Art]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sameSiteAs Context triple: [Moorilla Estate, sameSiteAs, Museum of Old and New Art]
-
A.
sameMatchAs
Indicates that two entities are considered equivalent or represent the same underlying match or correspondence in a given context.
-
B.
sameWorkAs
Indicates that two entities perform or are associated with the same work, job, or professional role.
-
C.
samePersonAs
Indicates that two referenced entities are in fact the very same individual, not just similar or related.
-
D.
inSameSystemAs
Indicates that two entities are located within or belong to the same overarching system or framework.
-
E.
similarSchemeIn
Indicates that one entity uses a scheme or structural pattern that is similar to that used in another entity.
- F. None of above. chosen
Provenance (4 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865578d48190bf90e470634fd97d |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f78575917481909a3defd6a4c366bd |
completed | May 3, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:01 p.m.