Triple
T32366729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TENAYA |
E827013
|
entity |
| Predicate | secondaryEndpointType |
P197422
|
FINISHED |
| Object | safety |
—
|
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: safety | Statement: [TENAYA, secondaryEndpointType, safety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryEndpointType Context triple: [TENAYA, secondaryEndpointType, safety]
-
A.
secondaryEndpoint
Indicates that something serves as an additional, non-primary endpoint or target associated with a main endpoint in a relationship or process.
-
B.
secondaryHub
Indicates that an entity functions as a secondary or backup hub in relation to a primary hub within a network or system.
-
C.
secondaryPort
Indicates that an entity serves as an additional or backup port associated with another primary port or connection.
-
D.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
E.
secondaryTarget
Indicates that an entity serves as an additional or subordinate target in relation to a primary target within a given context or action.
- F. None of above. chosen
Provenance (4 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe91383a1c81909266e40c3c3ede6c |
completed | May 9, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69fe8fde094081908f0f121664fbb5c7 |
completed | May 9, 2026, 1:37 a.m. |
| PDg | Predicate description generation | batch_69fe9137730c81909d1d57c30566c89a |
completed | May 9, 2026, 1:43 a.m. |
Created at: May 1, 2026, 12:50 a.m.