Triple
T20253490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iffland-Ring |
E498619
|
entity |
| Predicate | transferCondition |
P57864
|
FINISHED |
| Object | transferred upon death of the holder |
—
|
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: transferred upon death of the holder | Statement: [Iffland-Ring, transferCondition, transferred upon death of the holder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferCondition Context triple: [Iffland-Ring, transferCondition, transferred upon death of the holder]
-
A.
transmissionCondition
chosen
Indicates the circumstances or requirements under which something is transmitted from one entity to another.
-
B.
transferPolicy
Indicates a rule or set of conditions governing when and how something may be transferred from one party or location to another.
-
C.
transferAgreement
Indicates a formal arrangement in which ownership, rights, or responsibilities are transferred from one party to another.
-
D.
transferReason
Indicates the reason or justification for a transfer occurring between entities.
-
E.
transferFeature
Indicates a relationship where a feature, attribute, or capability is moved or reassigned from one entity to another.
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e673aa42348190852ae8313f4494ca |
completed | April 20, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:41 p.m.