Triple
T34694341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nova 2 |
E890984
|
entity |
| Predicate | relativePositionInFleet |
P125479
|
FINISHED |
| Object | earlier than Nova 3 |
—
|
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: earlier than Nova 3 | Statement: [Nova 2, relativePositionInFleet, earlier than Nova 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativePositionInFleet Context triple: [Nova 2, relativePositionInFleet, earlier than Nova 3]
-
A.
relativeSizeInFleet
Indicates the comparative size or capacity of an entity relative to other entities within the same fleet.
-
B.
relativePositionWithinTeam
chosen
Indicates the positional or hierarchical relationship an entity holds relative to other members within the same team.
-
C.
relativePositionInSystem
Indicates the spatial or ordered position an entity occupies within a larger system or structured arrangement.
-
D.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
E.
relativeImportanceInFleet
Indicates the comparative significance or priority of an entity within the context of a fleet.
- 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:05 a.m.