Triple
T4410462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project Daedalus |
E94839
|
entity |
| Predicate | realizationStatus |
P22521
|
FINISHED |
| Object | never built |
—
|
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: never built | Statement: [Project Daedalus, realizationStatus, never built]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realizationStatus Context triple: [Project Daedalus, realizationStatus, never built]
-
A.
realityStatus
Indicates the relationship between an entity and its state of existence or authenticity within a given context or world (e.g., real, fictional, hypothetical, simulated).
-
B.
hasRealizationAs
Indicates that something abstract, such as a plan, design, or concept, is concretely implemented or manifested as a particular realized form.
-
C.
implementationStatus
chosen
Indicates the current state or progress of carrying out or realizing something, such as a plan, design, or requirement.
-
D.
acquisitionStatus
Indicates the current state or outcome of an acquisition process between entities (e.g., pending, completed, failed, or canceled).
-
E.
commissionedStatus
Indicates whether an entity has been formally authorized, activated, or placed into official service or duty.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b354e4c58c8190b4190aad3095a1dd |
completed | March 13, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:29 p.m.