Triple
T36206070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Household of the King of Rome |
E1047399
|
entity |
| Predicate | residenceServed |
P178689
|
FINISHED |
| Object | Tuileries Palace |
—
|
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: Tuileries Palace | Statement: [Household of the King of Rome, residenceServed, Tuileries Palace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residenceServed Context triple: [Household of the King of Rome, residenceServed, Tuileries Palace]
-
A.
townServed
Indicates that a given service, facility, or infrastructure serves or provides coverage to a particular town.
-
B.
servesResidentialArea
Indicates that something provides services or functions to a particular residential area or neighborhood.
-
C.
inhabitantsServed
chosen
Indicates the relationship in which a service, facility, or resource provides for or meets the needs of a specified group of inhabitants.
-
D.
residesUnder
Indicates that one entity lives or is situated beneath another entity in a hierarchical or spatial structure.
-
E.
areaServed
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
- 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_69f76e414bdc8190996f15a544220a3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:08 p.m.