Triple
T37984548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sydney Cricket Ground Trust |
E947649
|
entity |
| Predicate | main building |
P39867
|
FINISHED |
| Object | Sydney Cricket Ground |
—
|
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: Sydney Cricket Ground | Statement: [Sydney Cricket Ground Trust, main building, Sydney Cricket Ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: main building Context triple: [Sydney Cricket Ground Trust, main building, Sydney Cricket Ground]
-
A.
mainBuildingName
Indicates the name that is designated as the primary or main building associated with an entity.
-
B.
isMainBuildingOf
chosen
Indicates that a building serves as the primary or central facility associated with a particular organization, complex, or site.
-
C.
mainBuildingServes
Indicates that a main building provides services, functions, or support to another entity or group of entities.
-
D.
publicBuilding
Indicates that a building is designated for public use or access, typically serving communal, governmental, or civic functions.
-
E.
building
Indicates that one entity constructs, assembles, or develops another entity, typically over a period of time.
- 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.