Triple
T3503527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FOIRL |
E74021
|
entity |
| Predicate | distanceAdvantageOver |
P21058
|
FINISHED |
| Object | copper-based Ethernet links |
—
|
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: copper-based Ethernet links | Statement: [FOIRL, distanceAdvantageOver, copper-based Ethernet links]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceAdvantageOver Context triple: [FOIRL, distanceAdvantageOver, copper-based Ethernet links]
-
A.
distance
Indicates the spatial separation or length between two points, objects, or locations.
-
B.
distanceCharacteristic
Indicates a relationship where an entity is described or constrained by some property or measure of distance (e.g., range, spacing, or separation).
-
C.
hasLongerReachThan
chosen
Indicates that one entity can extend, influence, or physically reach farther than another entity.
-
D.
distanceCategory
Indicates the qualitative classification of how far apart two entities are from each other (e.g., near, medium, far).
-
E.
notableAdvantage
Indicates that one entity possesses a significant benefit, edge, or favorable quality over another entity or in a given context.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbf0c2b48190b49923137bb9e45d |
completed | March 8, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69adae0cd8b0819099da300af09880da |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.