Triple
T37984876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paddington End |
E947659
|
entity |
| Predicate | governingBodyVenueOwner |
P204510
|
FINISHED |
| Object | Sydney Cricket and Sports Ground Trust |
E947649
|
NE 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: Sydney Cricket and Sports Ground Trust | Statement: [Paddington End, governingBodyVenueOwner, Sydney Cricket and Sports Ground Trust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingBodyVenueOwner Context triple: [Paddington End, governingBodyVenueOwner, Sydney Cricket and Sports Ground Trust]
-
A.
venueOwner
Indicates that one entity is the owner or proprietor responsible for a particular venue or event location.
-
B.
hasVenueOwner
Indicates that a particular venue is owned or controlled by a specific owner.
-
C.
hostsVenue
Indicates that an entity provides or manages a location where an event or activity takes place.
-
D.
hostVenueInstanceOf
Indicates that a specific host venue is an instance or concrete realization of a more general venue type or category.
-
E.
hasPrincipalVenue
Indicates that an entity has a primary or main venue where its activities, events, or operations predominantly take place.
- F. None of above. chosen
Provenance (5 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_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4193b1b584819087944cdf47b26378 |
completed | June 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:20 p.m.