Triple
T21940088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eesti vapp |
E541793
|
entity |
| Predicate | ajaloolineJärjepidevus |
P146625
|
FINISHED |
| Object | Eesti Vabariigi sümboolika 1918–1940 |
—
|
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: Eesti Vabariigi sümboolika 1918–1940 | Statement: [Eesti vapp, ajaloolineJärjepidevus, Eesti Vabariigi sümboolika 1918–1940]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ajaloolineJärjepidevus Context triple: [Eesti vapp, ajaloolineJärjepidevus, Eesti Vabariigi sümboolika 1918–1940]
-
A.
arity
Indicates the number of arguments or participants that a relation or function takes.
-
B.
juz
Indicates a judgment or evaluation made about one entity in relation to another.
-
C.
ally
Indicates a cooperative relationship in which one entity supports, assists, or aligns with another, often for mutual benefit or a shared goal.
-
D.
justified
Indicates that an action, belief, or decision is supported by sufficient reasons or evidence to be considered reasonable or warranted.
-
E.
reversible
Indicates that the relationship or process can proceed in both directions, allowing a return to the original state or configuration.
- 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12420b1cc81909b375891aedc0979 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
| PDg | Predicate description generation | batch_69e6fb6991948190a428c3c3bfd1c3b8 |
completed | April 21, 2026, 4:22 a.m. |
Created at: April 16, 2026, 7:55 p.m.