Triple
T17128599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5th Battalion, Royal Australian Regiment |
E415662
|
entity |
| Predicate | reRaised |
P103296
|
FINISHED |
| Object | 1977 |
—
|
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: 1977 | Statement: [5th Battalion, Royal Australian Regiment, reRaised, 1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reRaised Context triple: [5th Battalion, Royal Australian Regiment, reRaised, 1977]
-
A.
raisedAgain
chosen
Indicates that something which was previously raised or brought up is raised again at a later point.
-
B.
raisedFrom
Indicates that one entity has been elevated, derived, or brought up from another prior state, source, or condition.
-
C.
raisedOn
Indicates that an entity was nurtured, brought up, or spent its formative period in a particular place, environment, or context.
-
D.
raisedDuring
Indicates that one entity was brought up, nurtured, or developed within the time period or circumstances defined by another entity.
-
E.
raisedWith
Indicates that two or more entities grew up together in the same household or close environment during their formative years.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f0285a408190ae5e4c4679c07fbf |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.