Triple
T31189818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World War I memorial (Kenderes) |
E795149
|
entity |
| Predicate | honorsResidentsOf |
P178076
|
FINISHED |
| Object | Kenderes |
—
|
NE NERFINISHED |
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: Kenderes | Statement: [World War I memorial (Kenderes), honorsResidentsOf, Kenderes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorsResidentsOf Context triple: [World War I memorial (Kenderes), honorsResidentsOf, Kenderes]
-
A.
permanentResidents
Indicates that one entity is a long-term, officially recognized resident of another entity (such as a place, institution, or jurisdiction).
-
B.
coResident
Indicates that two or more entities live in the same residence or dwelling at the same time.
-
C.
usedForResidentsOf
Indicates that something is intended to be used by, or serves the needs of, people who reside in a particular place or region.
-
D.
hasNotableResident
Indicates that an entity is or has been a well-known or distinguished resident of a particular place or location.
-
E.
intendedResidents
Indicates the people or entities for whom a place, dwelling, or facility is designed or meant to be occupied by.
- 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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f707f380388190954b79d52a321921 |
completed | May 3, 2026, 8:31 a.m. |
Created at: April 29, 2026, 9:08 p.m.