Triple
T34746386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Casey |
E1001646
|
entity |
| Predicate | isSharedByNotableIndividualsIn |
P160320
|
FINISHED |
| Object | politics |
—
|
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: politics | Statement: [James Casey, isSharedByNotableIndividualsIn, politics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSharedByNotableIndividualsIn Context triple: [James Casey, isSharedByNotableIndividualsIn, politics]
-
A.
isBorneByNotablePeopleIn
chosen
Indicates that something (such as a name, title, or attribute) is carried or held by notable people within a specified place or context.
-
B.
hasNotablePeople
Indicates that certain people associated with an entity are distinguished or noteworthy in some recognized way.
-
C.
heldByNotablePerson
Indicates that an item, position, or role is possessed, occupied, or controlled by a person of notable public significance.
-
D.
namedForNotablePersonFrom
Indicates that one entity is named in honor of a notable person who originates from another specified place or group.
-
E.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
- 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.