Triple
T23450124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katie Nanna |
E567754
|
entity |
| Predicate | associatedAddress |
P4379
|
FINISHED |
| Object | 17 Cherry Tree Lane |
—
|
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: 17 Cherry Tree Lane | Statement: [Katie Nanna, associatedAddress, 17 Cherry Tree Lane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedAddress Context triple: [Katie Nanna, associatedAddress, 17 Cherry Tree Lane]
-
A.
associatedWithAddress
Indicates a relationship where an entity is linked or connected to a specific address.
-
B.
addressedThrough
Indicates that an issue, request, or communication is handled, resolved, or processed by means of a specified channel, method, or intermediary.
-
C.
associatedName
Indicates that one entity has an alternative or related name that is linked or connected to another entity.
-
D.
hasAddress
chosen
Indicates that an entity is associated with a specific address or location.
-
E.
associatedThrough
Indicates that two entities are connected or related to each other by means of a specified intermediary, context, or linkage.
- 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_69e2458b4c888190b1d7998f9862a558 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a64c1ee081908ba3adf5ce80d6a5 |
completed | April 29, 2026, 6:33 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:52 p.m.