Triple
T7295511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian territories |
E164510
|
entity |
| Predicate | typeIncludes |
P53933
|
FINISHED |
| Object | internal territories of Australia |
—
|
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: internal territories of Australia | Statement: [Australian territories, typeIncludes, internal territories of Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeIncludes Context triple: [Australian territories, typeIncludes, internal territories of Australia]
-
A.
classificationIncludes
chosen
Indicates that a broader classification category encompasses or contains a specified subclass, member, or element within its scope.
-
B.
includesPackage
Indicates that one entity contains or comes bundled with a particular package as part of its composition or offering.
-
C.
includesRouteType
Indicates that one entity’s set of routes contains or covers a specific type or category of route associated with another entity.
-
D.
includesElement
Indicates that one collection, set, or structure contains a specified element as a member or component.
-
E.
includesMatch
Indicates that one entity contains or encompasses a particular match or matching instance of 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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6eb8d0c6c8190b32cd08b9a5d96cc |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76c5fbc8190b378830082f11cb0 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3 p.m.