Triple
T29304985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AppleTalk addressing |
E743066
|
entity |
| Predicate | addressUniquenessEnsuredBy |
P38254
|
FINISHED |
| Object | AARP probing |
—
|
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: AARP probing | Statement: [AppleTalk addressing, addressUniquenessEnsuredBy, AARP probing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressUniquenessEnsuredBy Context triple: [AppleTalk addressing, addressUniquenessEnsuredBy, AARP probing]
-
A.
canAddress
Indicates that one entity has the ability or permission to direct communication, action, or service toward another entity.
-
B.
membershipUniqueness
Indicates that each member in a given context is uniquely associated with a single group, role, or collection, preventing duplicate or overlapping memberships.
-
C.
associatedWithAddress
Indicates a relationship where an entity is linked or connected to a specific address.
-
D.
uniquenessCondition
chosen
Indicates that a specified element, value, or combination of attributes must be unique within a given set, context, or domain, with no duplicates allowed.
-
E.
hasAddress
Indicates that an entity is associated with a specific address or location.
- 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_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 1:12 p.m.