Triple
T25423664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melba |
E637054
|
entity |
| Predicate | hasStateOrTerritory |
P84299
|
FINISHED |
| Object | Australian Capital Territory |
—
|
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: Australian Capital Territory | Statement: [Melba, hasStateOrTerritory, Australian Capital Territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStateOrTerritory Context triple: [Melba, hasStateOrTerritory, Australian Capital Territory]
-
A.
hasStateOrDistrict
chosen
Indicates that an entity is associated with, located in, or belongs to a particular state or district.
-
B.
stateOrTerritory
Indicates that one entity is a state or territory that is politically or administratively associated with another entity.
-
C.
isInUSState
Indicates that one entity (typically a place or location) is geographically located within the boundaries of a specific U.S. state.
-
D.
hasLegislativeState
Indicates that an entity is associated with, governed by, or falls under the jurisdiction of a particular legislative state or lawmaking authority.
-
E.
usedByStateOrTerritory
Indicates that something (such as an object, system, or resource) is utilized or employed by a specific state or territory.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 21, 2026, 1:57 p.m.