Triple
T12352782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Leuchtenberg |
E294532
|
entity |
| Predicate | acquiredStatus |
P38040
|
FINISHED |
| Object | Russian imperial family branch |
—
|
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: Russian imperial family branch | Statement: [House of Leuchtenberg, acquiredStatus, Russian imperial family branch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquiredStatus Context triple: [House of Leuchtenberg, acquiredStatus, Russian imperial family branch]
-
A.
acquisitionStatus
Indicates the current state or outcome of an acquisition process between entities (e.g., pending, completed, failed, or canceled).
-
B.
obtainedStatus
chosen
Indicates that an entity has received or achieved a particular status or condition as a result of some process or event.
-
C.
acquiredFor
Indicates that one entity obtained or purchased another entity specifically for the benefit, use, or purpose of a third entity.
-
D.
postAcquisitionStatus
Indicates the condition or state of an entity after it has been acquired by another party.
-
E.
acquiredWith
Indicates that one entity was obtained, purchased, or gained together with or by means of another entity.
- 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f8aa33c8190b22b7dff9559b8ed |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.