Triple
T26235617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Family Court of Australia |
E656156
|
entity |
| Predicate | hasPrincipalRegistryLocation |
P89056
|
FINISHED |
| Object | Sydney |
—
|
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 | Statement: [Family Court of Australia, hasPrincipalRegistryLocation, Sydney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrincipalRegistryLocation Context triple: [Family Court of Australia, hasPrincipalRegistryLocation, Sydney]
-
A.
hasRegistrar
Indicates that an entity is formally recorded or overseen by a specific registrar organization or authority.
-
B.
hasPrimaryAssetLocation
Indicates that an entity’s main or principal asset is located at a specified place or facility.
-
C.
hasDistrictRegistries
chosen
Indicates that an entity maintains or is associated with one or more official registries at the district level.
-
D.
hasPrimaryLocationSetting
Indicates that an entity is associated with its main or default geographic or contextual location.
-
E.
hasKeyLocation
Indicates that an entity possesses or is associated with a specific primary or important location relevant to it.
- 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 26, 2026, 9:01 p.m.