Triple
T29304967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AppleTalk addressing |
E743066
|
entity |
| Predicate | reservedNodeNumbersUsage |
P117704
|
FINISHED |
| Object | special purposes |
—
|
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: special purposes | Statement: [AppleTalk addressing, reservedNodeNumbersUsage, special purposes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservedNodeNumbersUsage Context triple: [AppleTalk addressing, reservedNodeNumbersUsage, special purposes]
-
A.
nodeNumber
Indicates that an entity is assigned a specific numerical identifier representing its position or index within a node-based structure.
-
B.
previouslyUsedNumberDesignationsUntil
Indicates that certain number designations were used for an entity up until a specified point in time, after which they were no longer in use.
-
C.
nodeNumberSize
Indicates the size or magnitude associated with a node’s numerical identifier or value.
-
D.
registersUsed
Indicates that certain registers are utilized or occupied by a given operation, instruction, or computational entity.
-
E.
numberPool
chosen
Indicates that an entity is associated with or belongs to a specific pool or collection of numbers.
- 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_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 1:12 p.m.