Triple
T2998385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10BASE5 |
E81124
|
entity |
| Predicate | wasCommonIn |
P7254
|
FINISHED |
| Object | early corporate LAN backbones |
—
|
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: early corporate LAN backbones | Statement: [10BASE5, wasCommonIn, early corporate LAN backbones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCommonIn Context triple: [10BASE5, wasCommonIn, early corporate LAN backbones]
-
A.
moreCommonIn
Indicates that something occurs with greater frequency or prevalence in one group, context, or location than in another.
-
B.
commonIn
chosen
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
C.
wasAmong
Indicates that an entity belonged to, was included in, or was part of a particular group, set, or collection.
-
D.
wasIn
Indicates that an entity existed, occurred, or was located within a particular place or context during a specified time or situation.
-
E.
widelyUsedIn
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99f766408190a5591efce8346bb9 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.