Triple
T31598650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eagle V |
E806285
|
entity |
| Predicate | relativeToPredecessor |
—
|
GENERATED |
| Object | updated iteration |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeToPredecessor Context triple: [Eagle V, relativeToPredecessor, updated iteration]
-
A.
distanceFromPredecessor
Indicates the measured distance separating an entity from the one that immediately precedes it in a sequence or ordering.
-
B.
comparedToPredecessor
chosen
Indicates that something is being evaluated or measured in relation to the thing that came immediately before it.
-
C.
predecessorRelationship
Indicates that one entity comes before another in an ordered sequence, chain, or lineage, serving as its prior or earlier counterpart.
-
D.
intendedPredecessorOf
Indicates that one entity is meant or planned to come before another in a sequence, order, or process.
-
E.
ownedByPredecessor
Indicates that something is or was owned by an entity that previously held a given role, position, or status before the current one.
- F. None of above.
Provenance (1 batch)
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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:31 p.m.