Triple
T27210887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian 18th Brigade |
E683992
|
entity |
| Predicate | laterAssignedTo |
P146596
|
FINISHED |
| Object | 6th Australian Division |
—
|
NE NERFINISHED |
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: 6th Australian Division | Statement: [Australian 18th Brigade, laterAssignedTo, 6th Australian Division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterAssignedTo Context triple: [Australian 18th Brigade, laterAssignedTo, 6th Australian Division]
-
A.
assignedTo
Indicates that responsibility for a task, item, or role has been designated to a specific entity.
-
B.
assignedAs
Indicates that one entity is designated or appointed to perform a specific role, task, or function in relation to another entity.
-
C.
historicallyAssignedTo
Indicates that something was associated with or allocated to a particular entity during a past period, but may no longer be so in the present.
-
D.
laterAssignment
chosen
Indicates that one entity is assigned or allocated to another at a later time than some reference assignment or event.
-
E.
assignedToWorkBy
Indicates that one entity is designated or directed by another entity to perform a specific job, task, or role.
- 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 27, 2026, 9:39 a.m.