Triple
T25864126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Val-Richer |
E651564
|
entity |
| Predicate | associatedWithOccupationOfResident |
P83547
|
FINISHED |
| Object | statesman |
—
|
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: statesman | Statement: [Val-Richer, associatedWithOccupationOfResident, statesman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithOccupationOfResident Context triple: [Val-Richer, associatedWithOccupationOfResident, statesman]
-
A.
hasOccupationOfResident
Indicates that one entity holds the role or status of being a resident in relation to another entity or context.
-
B.
significantResidentOccupation
Indicates that a resident’s occupation is notably important or defining in the context of their residence or community.
-
C.
occupationOfAssociatedPerson
chosen
Indicates the job or professional role held by a person who is associated with another referenced entity.
-
D.
jurisdictionOfOccupant
Indicates the legal authority or control that an occupant exercises over a place, property, or domain.
-
E.
residesUnder
Indicates that one entity lives or is situated beneath another entity in a hierarchical or spatial structure.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
Created at: April 22, 2026, 8:06 a.m.