Triple
T8084569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jim Rockford |
E188697
|
entity |
| Predicate | telephoneNumber |
P5467
|
FINISHED |
| Object | 555-2368 |
—
|
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: 555-2368 | Statement: [Jim Rockford, telephoneNumber, 555-2368]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telephoneNumber Context triple: [Jim Rockford, telephoneNumber, 555-2368]
-
A.
associatedNumber
chosen
Indicates a relationship where a specific number is linked or assigned to an entity as its associated value.
-
B.
officeNumber
Indicates the specific room or suite number assigned to an office within a building or complex.
-
C.
emergencyPhoneNumber
Indicates that the object is a phone number designated for use in emergencies or urgent situations.
-
D.
telephoneStandard
Indicates that there is a relationship involving the use of a particular telephone standard or protocol for communication between entities.
-
E.
hasTelephoneService
Indicates that a subject is provided with or connected to telephone service.
- 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_69ca82b662e88190b9323daab8c28a21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb415e61ac81909e924aea69a7ff77 |
completed | March 31, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:29 p.m.