Triple
T14493437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Army Reserve |
E359423
|
entity |
| Predicate | canBeCalledOutFor |
P114444
|
FINISHED |
| Object | defence 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: defence of Australia | Statement: [Australian Army Reserve, canBeCalledOutFor, defence of Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeCalledOutFor Context triple: [Australian Army Reserve, canBeCalledOutFor, defence of Australia]
-
A.
canBeCalledTo
Indicates that one entity is able or permitted to initiate a call or summon another entity.
-
B.
canBeCalled
Indicates that one entity is able or permitted to be addressed, referred to, or named by another entity in a particular way.
-
C.
canBeCalledInto
Indicates that one entity has the authority or ability to summon, request the presence of, or formally convene another entity.
-
D.
canBeAppealedTo
Indicates that a decision, action, or authority is subject to being challenged or reviewed by a higher or alternative authority through an appeal process.
-
E.
canBeSuedFor
Indicates that one party is legally liable or potentially subject to legal action by another party for a specified cause or wrongdoing.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de930f34d08190b4b30e54e2f702ed |
completed | April 14, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:21 a.m.