Triple
T1430474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rendezvous With Destiny |
E30431
|
entity |
| Predicate | associatedUnitType |
P28425
|
FINISHED |
| Object | airborne division |
—
|
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: airborne division | Statement: [Rendezvous With Destiny, associatedUnitType, airborne division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedUnitType Context triple: [Rendezvous With Destiny, associatedUnitType, airborne division]
-
A.
associatedWithUnit
Indicates that one entity has a connection, linkage, or affiliation with a particular unit (such as a division, department, or organizational subunit).
-
B.
basedUnitType
Indicates that one unit is defined or derived in terms of another underlying (base) unit type.
-
C.
involvedUnit
Indicates that a particular unit (such as a group, organization, or division) participates in, is associated with, or plays a role in the referenced event or activity.
-
D.
basedUnit
Indicates that one unit is defined in terms of, or derived from, another more fundamental unit.
-
E.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
- 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c500a9888190a16fbb1ec97a79c9 |
completed | March 1, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69a4c4771c9481908ae47c959debbe77 |
completed | March 1, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69a4c4feea448190b2b5071b28a5b608 |
completed | March 1, 2026, 11 p.m. |
Created at: March 1, 2026, 8 p.m.