Triple
T5567726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commonwealth Star |
E145919
|
entity |
| Predicate | additionalPointRepresents |
P50729
|
FINISHED |
| Object | Australian territories |
—
|
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: Australian territories | Statement: [Commonwealth Star, additionalPointRepresents, Australian territories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: additionalPointRepresents Context triple: [Commonwealth Star, additionalPointRepresents, Australian territories]
-
A.
entéEnPointRepresents
chosen
Indicates that an entity is represented or depicted by a specific point in some reference space or coordinate system.
-
B.
additionalLocation
Indicates that an entity has one or more extra or secondary locations associated with it beyond its primary location.
-
C.
interactionPoint
Indicates a specific location or moment where two or more entities come into contact or engage with each other.
-
D.
isReferencePointFor
Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
-
E.
pointDefinition
Indicates that one entity serves as the defining description or specification of a particular point in another entity.
- 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.