Triple
T9029789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G.fast |
E216138
|
entity |
| Predicate | compatibleWithInfrastructure |
P48645
|
FINISHED |
| Object | existing copper telephone wiring |
—
|
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: existing copper telephone wiring | Statement: [G.fast, compatibleWithInfrastructure, existing copper telephone wiring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compatibleWithInfrastructure Context triple: [G.fast, compatibleWithInfrastructure, existing copper telephone wiring]
-
A.
usesInfrastructure
Indicates that one entity makes use of, depends on, or operates through the infrastructure provided or managed by another entity.
-
B.
supportsInfrastructure
Indicates that one entity provides resources, services, or capabilities that enable the operation, maintenance, or development of another entity’s infrastructure.
-
C.
compatibleSign
Indicates that two entities are considered astrologically harmonious or well-matched based on their zodiac signs.
-
D.
compatibleStand
Indicates that one entity can be properly supported or held by another entity’s stand or mounting system.
-
E.
isGenerallyCompatibleWith
chosen
Indicates that two entities can typically function or coexist together without significant conflict, issues, or need for special adaptation.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a9bcb508190b58751f1772407d4 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:08 p.m.