Triple
T5013195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Jones |
E112675
|
entity |
| Predicate | associatedPersonNationality |
P33828
|
FINISHED |
| Object | British |
—
|
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: British | Statement: [John Jones, associatedPersonNationality, British]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPersonNationality Context triple: [John Jones, associatedPersonNationality, British]
-
A.
associatedWithNationality
chosen
Indicates that one entity has a connection or affiliation with the nationality of another entity.
-
B.
associatedWithNotableBearerNationality
Indicates that an entity is connected to the nationality of a notable bearer of a related name or title.
-
C.
bearerNationality
Indicates that one entity is the country or nationality associated with the bearer of another entity, such as a document or credential.
-
D.
nationalityInText
Indicates that a person's nationality is mentioned or specified within a given text.
-
E.
includedNationality
Indicates that one entity’s set of nationalities contains or encompasses the nationality of 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd730f12a481908a27c15dc73987c6 |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.