Triple
T36438805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Nassau-Usingen |
E897667
|
entity |
| Predicate | territorialHouse |
P185505
|
FINISHED |
| Object | House of Nassau-Weilburg |
E15163
|
NE 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: House of Nassau-Weilburg | Statement: [Prince of Nassau-Usingen, territorialHouse, House of Nassau-Weilburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: territorialHouse Context triple: [Prince of Nassau-Usingen, territorialHouse, House of Nassau-Weilburg]
-
A.
territorial
Indicates that one entity claims, defends, or is associated with control over a specific area or domain in relation to another entity.
-
B.
house1
Indicates that something is identified or classified as a house or dwelling.
-
C.
domesticStructure
Indicates a structural or organizational relationship within a household or domestic setting, such as how roles, responsibilities, or living arrangements are arranged among its members.
-
D.
typicalHouse
Indicates that something is a standard or representative example of a house in terms of its usual features, structure, or characteristics.
-
E.
houseLocatedIn
Indicates that a house is situated within or belongs to a specific geographic location or area.
- F. None of above. chosen
Provenance (5 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_69f76e56636481908eda808ab0273401 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39f8faf2f48190b32980ad9353f7f8 |
completed | June 23, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:10 p.m.