Triple
T17073007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4th Battalion, Royal Australian Regiment |
E414267
|
entity |
| Predicate | dateOfConversionToCommando |
P10480
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [4th Battalion, Royal Australian Regiment, dateOfConversionToCommando, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfConversionToCommando Context triple: [4th Battalion, Royal Australian Regiment, dateOfConversionToCommando, 1997]
-
A.
dateAsActingCommander
Indicates the date on which an entity served in the role of acting commander.
-
B.
dateOfConversion
chosen
Indicates the specific date on which an entity changed status, form, or affiliation (e.g., religious, legal, or organizational conversion).
-
C.
ordinationDate
Indicates the date on which an individual was formally ordained to a religious office or role.
-
D.
commandedTo
Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
-
E.
dateOfConversionToPrison
Indicates the date on which an entity was converted, reclassified, or officially designated as a prison.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc28fec81909c39d432094d9cdd |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.