Triple
T27945626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPX |
E700871
|
entity |
| Predicate | addressingUses |
P165725
|
FINISHED |
| Object | IPX network address |
—
|
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: IPX network address | Statement: [SPX, addressingUses, IPX network address]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressingUses Context triple: [SPX, addressingUses, IPX network address]
-
A.
addressing
Indicates that one entity is directing speech, communication, or attention specifically toward another entity.
-
B.
addressingSupport
Indicates that one entity provides assistance or resources to help another entity address or resolve a specific issue, need, or challenge.
-
C.
eligibleUses
Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
-
D.
endedUseWith
Indicates that an entity has stopped or terminated its use or association with another entity.
-
E.
designationUsedFor
Indicates that a particular name, label, or title is employed to refer to or identify a specific entity or role.
- F. None of above. chosen
Provenance (4 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a6babcc81908052c9907a99c882 |
completed | May 2, 2026, 8:11 p.m. |
Created at: April 27, 2026, 7:21 p.m.