Triple
T35986968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Garden at Trianon |
E1040736
|
entity |
| Predicate | withinSite |
P5003
|
FINISHED |
| Object | Trianon palaces and gardens |
—
|
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: Trianon palaces and gardens | Statement: [Royal Garden at Trianon, withinSite, Trianon palaces and gardens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withinSite Context triple: [Royal Garden at Trianon, withinSite, Trianon palaces and gardens]
-
A.
containsSite
chosen
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
-
B.
isSiteOf
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
C.
numberWithinSite
Indicates that an entity has a specific identifying number or position assigned within the context of a particular site or location.
-
D.
isTypeSiteOf
Indicates that a site serves as the specific location or setting where a particular type, category, or classification is realized or occurs.
-
E.
currentSiteUse
Indicates how a site is presently being used or the function it currently serves.
- 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:07 p.m.