Triple
T9312946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B-root |
E224047
|
entity |
| Predicate | criticality |
P88025
|
FINISHED |
| Object | critical internet infrastructure |
—
|
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: critical internet infrastructure | Statement: [B-root, criticality, critical internet infrastructure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: criticality Context triple: [B-root, criticality, critical internet infrastructure]
-
A.
criticalStrip
Indicates that something lies within the critical strip, the region of complex values whose real parts fall between 0 and 1.
-
B.
criticalApproach
Indicates that an entity employs an analytical, questioning, or evaluative method toward another entity, concept, or work.
-
C.
criticalReputation
Indicates that an entity is regarded by critics with a particular level or type of esteem, evaluation, or standing based on critical assessments.
-
D.
criticalReception
Indicates how a work, performance, or product is evaluated and responded to by critics or professional reviewers.
-
E.
criticalLine
Indicates that one entity is a crucial or decisive line (such as a boundary, path, or threshold) whose state or position significantly affects the other entity or overall system.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20ae96e481909a1af9ea1c91f2b2 |
completed | April 1, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:37 p.m.