Triple
T12942191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heart’s Needle |
E309662
|
entity |
| Predicate | addressesPerson |
P265
|
FINISHED |
| Object | poet’s young daughter |
—
|
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: poet’s young daughter | Statement: [Heart’s Needle, addressesPerson, poet’s young daughter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressesPerson Context triple: [Heart’s Needle, addressesPerson, poet’s young daughter]
-
A.
addresses
chosen
Indicates that one entity directs speech, communication, or written correspondence specifically toward another entity.
-
B.
addressType
Indicates the specific kind or category of address associated with an entity (e.g., home, work, billing, or shipping).
-
C.
address
Indicates that one entity directs spoken or written communication specifically to another entity.
-
D.
addressesPosition
Indicates that one entity communicates with, responds to, or deals with the role, status, or job position held by another entity.
-
E.
addressesWork
Indicates that one entity directs or delivers work-related communication or correspondence to another entity.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:43 p.m.