Triple
T38183797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phillip Street |
E1005247
|
entity |
| Predicate | isPartOfPrecinct |
P117385
|
FINISHED |
| Object | Sydney legal precinct |
—
|
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: Sydney legal precinct | Statement: [Phillip Street, isPartOfPrecinct, Sydney legal precinct]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfPrecinct Context triple: [Phillip Street, isPartOfPrecinct, Sydney legal precinct]
-
A.
partOfPrecinct
chosen
Indicates that one entity is a subdivision or component contained within a specific precinct.
-
B.
isMajorPrecinctFor
Indicates that one entity serves as the primary or main precinct responsible for another entity within a given jurisdiction or context.
-
C.
hasNumberedPrecinct
Indicates that an entity is associated with a specific precinct identified by a number.
-
D.
hasInnerPrecinct
Indicates that one area, structure, or zone contains another, more central or enclosed precinct within its boundaries.
-
E.
hasParentPrecinctSystem
Indicates that one precinct system functions as the parent or higher-level organizational unit of another precinct system.
- 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a002ae74da08190a4b47e0ff0f7f8fe |
completed | May 10, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_6a0029cc369c81909578e52c4a75ab18 |
completed | May 10, 2026, 6:46 a.m. |
Created at: May 3, 2026, 4:29 p.m.