Triple
T19647560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AGTC |
E471718
|
entity |
| Predicate | coversInfrastructure |
P11065
|
FINISHED |
| Object | terminals |
—
|
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: terminals | Statement: [AGTC, coversInfrastructure, terminals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversInfrastructure Context triple: [AGTC, coversInfrastructure, terminals]
-
A.
containedInfrastructure
Indicates that one infrastructure element is physically or logically contained within another infrastructure element.
-
B.
usesInfrastructure
Indicates that one entity makes use of, depends on, or operates through the infrastructure provided or managed by another entity.
-
C.
parallelInfrastructure
Indicates that two or more infrastructure elements are arranged or operate in parallel to each other, typically serving similar functions simultaneously.
-
D.
supportsInfrastructure
chosen
Indicates that one entity provides resources, services, or capabilities that enable the operation, maintenance, or development of another entity’s infrastructure.
-
E.
relatedInfrastructure
Indicates that one piece of infrastructure is connected, associated, or functionally related to another infrastructure element.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64125dd9481908a891c71c975a964 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.