Triple
T25864130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Val-Richer |
E651564
|
entity |
| Predicate | associatedWithFieldOfResident |
P196238
|
FINISHED |
| Object | historiography |
—
|
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: historiography | Statement: [Val-Richer, associatedWithFieldOfResident, historiography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFieldOfResident Context triple: [Val-Richer, associatedWithFieldOfResident, historiography]
-
A.
associatedResidenceForElectors
Indicates that a particular residence is officially linked to or recorded for a given elector.
-
B.
residesUnder
Indicates that one entity lives or is situated beneath another entity in a hierarchical or spatial structure.
-
C.
aliasOfResident
Indicates that one entity is an alternative name or alias used for a resident entity.
-
D.
associatedWithLocality
Indicates a relationship where something has a connection or relevance to a specific geographic place or locality.
-
E.
residesNear
Indicates that one entity lives or is located in close physical proximity to another entity.
- F. None of above. chosen
Provenance (4 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_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fe189f2ea48190b8c4718f1353970e |
completed | May 8, 2026, 5:08 p.m. |
Created at: April 22, 2026, 8:06 a.m.