Triple
T28977918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Topthorn |
E734462
|
entity |
| Predicate | laterBelongsToUnit |
P196116
|
FINISHED |
| Object | German army |
—
|
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: German army | Statement: [Topthorn, laterBelongsToUnit, German army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterBelongsToUnit Context triple: [Topthorn, laterBelongsToUnit, German army]
-
A.
assignedToUnit
Indicates that an entity (such as a person, resource, or task) is allocated or designated to a specific unit or organizational subdivision.
-
B.
associatedWithUnit
Indicates that one entity has a connection, linkage, or affiliation with a particular unit (such as a division, department, or organizational subunit).
-
C.
followsUnit
Indicates that one unit comes directly after or is ordered subsequent to another unit in a sequence or structure.
-
D.
successorUnitIntegratedInto
Indicates that a subsequent or replacement unit has been incorporated into, or merged with, another unit as part of an organizational or structural succession.
-
E.
associatedUnitType
Indicates that one entity is linked to or characterized by a particular type or category of unit.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
| PDg | Predicate description generation | batch_69fe08d1b3f881908eccb74cb0d246dc |
completed | May 8, 2026, 4:01 p.m. |
Created at: April 28, 2026, 9:09 a.m.