Triple
T29304961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AppleTalk addressing |
E743066
|
entity |
| Predicate | addressScope |
P74850
|
FINISHED |
| Object | cable range |
—
|
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: cable range | Statement: [AppleTalk addressing, addressScope, cable range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressScope Context triple: [AppleTalk addressing, addressScope, cable range]
-
A.
locationScope
Indicates the specific geographic or spatial area within which a given relationship, condition, or action is considered valid or applicable.
-
B.
addressArea
chosen
Indicates the geographic area or region that an address is located in or associated with.
-
C.
addressContext
Indicates the situational or conversational setting in which an address (such as a location, contact, or reference) is used or interpreted.
-
D.
addressLocal
Indicates that one entity serves as a local or nearby address or location reference for another entity.
-
E.
addressesCondition
Indicates that an action, intervention, or entity is intended to treat, manage, or otherwise respond to a specified condition or problem.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 1:12 p.m.