Triple
T29116646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zweibrücken-Birkenfeld |
E737062
|
entity |
| Predicate | hadEstates |
P166348
|
FINISHED |
| Object | nobility |
—
|
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: nobility | Statement: [Zweibrücken-Birkenfeld, hadEstates, nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadEstates Context triple: [Zweibrücken-Birkenfeld, hadEstates, nobility]
-
A.
hadEstate
Indicates that an entity possessed or owned a particular estate or landed property.
-
B.
hadEstatesAssembly
Indicates that an entity possessed or was associated with a legislative or deliberative estates assembly (such as a representative body of estates or orders).
-
C.
hasNearbyHistoricalEstate
Indicates that one entity is located close to another entity that is a recognized historical estate.
-
D.
heirOfEstate
Indicates that one entity is legally designated to inherit the estate or property of another entity, typically upon that entity’s death.
-
E.
originalEstates
Indicates that an entity is associated with or represents the initial or primary estates from which subsequent rights, interests, or derived estates originate.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f661f1378c8190aa0ffc365dfb589f |
completed | May 2, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 11:22 a.m.