Triple
T29654969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Immortal |
E750239
|
entity |
| Predicate | techRequirement |
P60268
|
FINISHED |
| Object | Robotics Facility |
—
|
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: Robotics Facility | Statement: [Immortal, techRequirement, Robotics Facility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: techRequirement Context triple: [Immortal, techRequirement, Robotics Facility]
-
A.
platformRequirement
Indicates that one entity specifies a necessary platform or environment condition that must be met for another entity to function or be applicable.
-
B.
unitRequirement
Indicates that one entity specifies a required quantity or unit that another entity must meet or conform to.
-
C.
technicalDemand
chosen
Indicates that one entity requires or imposes a certain level of technical skill, complexity, or resources on another entity.
-
D.
requiresSoftware
Indicates that one entity depends on specific software being present or installed in order to function, operate, or be used.
-
E.
componentRequirement
Indicates that one component depends on or necessitates the presence or use of another component to function or be considered complete.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f66f274ba08190bcdbdfeccf4af09d |
completed | May 2, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:54 p.m.