Triple
T5567910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Hall, Sydney |
E145923
|
entity |
| Predicate | eventDateAtSite |
P51947
|
FINISHED |
| Object | 26 January 1938 |
—
|
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: 26 January 1938 | Statement: [Australian Hall, Sydney, eventDateAtSite, 26 January 1938]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventDateAtSite Context triple: [Australian Hall, Sydney, eventDateAtSite, 26 January 1938]
-
A.
eventDateAtLocation
chosen
Indicates that a specific event occurs on a particular date at a given location.
-
B.
eventOccurredAt
Indicates that a particular event took place at a specific time or location.
-
C.
eventStartDateOrganized
Indicates the date on which an event is formally scheduled or organized to begin.
-
D.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
-
E.
eventLocationOfNotableActivity
Indicates that a location is the place where a notable or significant activity or event involving the related entity occurred.
- 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_69c008fdae24819081aa002ad99cd966 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0203631c881908978d51e99155014 |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b12826c8190969a584d0f53aa44 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.