Triple
T11325852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philip III, Count of Nassau-Weilburg |
E268214
|
entity |
| Predicate | realmLocatedIn |
P17086
|
FINISHED |
| Object | western Germany |
—
|
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: western Germany | Statement: [Philip III, Count of Nassau-Weilburg, realmLocatedIn, western Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realmLocatedIn Context triple: [Philip III, Count of Nassau-Weilburg, realmLocatedIn, western Germany]
-
A.
realmWithin
Indicates that one realm or domain is contained inside, or exists as a subset of, another realm or domain.
-
B.
regionSeatLocatedIn
Indicates that the administrative seat or capital of a region is located within that region.
-
C.
locatedOnTerritoryOf
chosen
Indicates that one entity is situated within or on the land area governed or owned by another entity.
-
D.
definedTerritoryOf
Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another entity.
-
E.
timeLocatedIn
Indicates that an event, state, or entity occurs, exists, or is valid within a specified time or temporal interval.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9e2253881909518cad0f12ef612 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.