Triple
T38072826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enoggera, Queensland |
E950629
|
entity |
| Predicate | hasDefenceRole |
P201065
|
FINISHED |
| Object | major Army garrison location |
—
|
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: major Army garrison location | Statement: [Enoggera, Queensland, hasDefenceRole, major Army garrison location]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDefenceRole Context triple: [Enoggera, Queensland, hasDefenceRole, major Army garrison location]
-
A.
hasDefensiveForce
Indicates that one entity possesses or maintains a defensive capability, protection, or force directed toward or associated with another entity.
-
B.
hasDefensiveType
Indicates that an entity possesses or is associated with a particular defensive category, attribute, or capability used for protection.
-
C.
hasDefensiveWork
Indicates that an entity possesses or is associated with a work focused on defense or protective functions.
-
D.
hasDefenseStrategy
Indicates that an entity employs or is associated with a particular plan or set of measures designed to protect against threats or attacks.
-
E.
providesDefence
Indicates that one entity offers protection or defensive support to another entity.
- F. None of above. chosen
Provenance (4 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffc516d1908190b475f5a6156b0ca8 |
completed | May 9, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69ffc4a946e08190b3535a5dc15ac484 |
completed | May 9, 2026, 11:35 p.m. |
| PDg | Predicate description generation | batch_69ffc515e4b08190810b2a29b2885162 |
completed | May 9, 2026, 11:36 p.m. |
Created at: May 3, 2026, 4:21 p.m.