Triple
T26145345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arms of the House of Lippe |
E659645
|
entity |
| Predicate | chargeCenter |
P160344
|
FINISHED |
| Object | golden seed |
—
|
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: golden seed | Statement: [Arms of the House of Lippe, chargeCenter, golden seed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargeCenter Context triple: [Arms of the House of Lippe, chargeCenter, golden seed]
-
A.
centralCharge
Indicates that an entity has a specific central charge value, typically quantifying a key parameter in a conformal or related physical or mathematical theory.
-
B.
chargeOnChief
Indicates that a formal accusation or legal charge is filed against a chief or primary authority figure.
-
C.
charge
Indicates that one entity formally accuses another of an offense or imposes a financial cost or obligation on them.
-
D.
hasCentralCharge
Indicates that an entity is associated with, or characterized by, a specific central charge value in a given theoretical or physical framework.
-
E.
chargeType
Indicates the category or nature of a charge applied in a transaction or interaction between entities (e.g., fee type, billing classification, or legal charge type).
- 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_69ee5bc496a88190af7deb7ab5e081de |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f60be803c88190980a8aafa935a52b |
completed | May 2, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 26, 2026, 8:22 p.m.