Triple
T10503610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Romania |
E247730
|
entity |
| Predicate | readoptedWithCrown |
P94534
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Coat of arms of Romania, readoptedWithCrown, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readoptedWithCrown Context triple: [Coat of arms of Romania, readoptedWithCrown, 2016]
-
A.
readopted
Indicates that an entity adopts again something or someone it had previously adopted, after a period of not holding that adoption.
-
B.
readoptedDeFacto
Indicates that an entity has been taken back or resumed in practice (though not necessarily through formal or legal means) after having been previously discontinued or relinquished.
-
C.
adoptedAsHeir
Indicates that one entity has been formally chosen and accepted as the legal heir or successor of another entity.
-
D.
crownedBy
Indicates that an entity is formally invested with a rank, title, or authority through a crowning ceremony performed by another entity.
-
E.
crownedWith
Indicates that one entity serves as a crown, top, or decorative upper covering placed upon another entity.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5099d62408190a6c6884411c6e423 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe46a6448190b061bc3545835cad |
completed | April 7, 2026, 12:53 p.m. |
Created at: April 6, 2026, 12:26 p.m.