Triple
T28519138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Beam |
E721708
|
entity |
| Predicate | endpointGuardian |
P140830
|
FINISHED |
| Object | Bear Guardian |
—
|
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: Bear Guardian | Statement: [the Beam, endpointGuardian, Bear Guardian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endpointGuardian Context triple: [the Beam, endpointGuardian, Bear Guardian]
-
A.
guardDuty
chosen
Indicates that one entity is responsible for protecting, watching over, or standing watch for another entity or location.
-
B.
featuresShield
Indicates that an entity includes or is equipped with a shield as one of its characteristics or components.
-
C.
helpedSecure
Indicates that one entity contributed to obtaining, protecting, or ensuring the safety or stability of another entity or outcome.
-
D.
endpointFeature
Indicates that a particular feature, capability, or characteristic is associated with, provided by, or available at a specific endpoint.
-
E.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64fa087648190abaf756ae4e8375c |
completed | May 2, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:19 a.m.