Triple
T28718428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | space habitat Elysium |
E730024
|
entity |
| Predicate | securityHead |
P168580
|
FINISHED |
| Object | Jessica Delacourt |
—
|
NE NERFINISHED |
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: Jessica Delacourt | Statement: [space habitat Elysium, securityHead, Jessica Delacourt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityHead Context triple: [space habitat Elysium, securityHead, Jessica Delacourt]
-
A.
securityPillar
Indicates that one entity functions as a foundational security pillar or core security domain in relation to another entity.
-
B.
security
Indicates that an entity provides protection, safety measures, or safeguards to another entity or against specific threats or risks.
-
C.
securityFigure
chosen
Indicates that one entity serves as a protective or safeguarding presence for another, typically responsible for ensuring its safety or security.
-
D.
securityAttention
Indicates that an entity is the focus of monitoring, concern, or scrutiny from a security perspective.
-
E.
securityAspect
Indicates a relationship where something pertains to, represents, or characterizes a particular aspect or dimension of security.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 28, 2026, 5:52 a.m.