Triple
T21940105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eesti vapp |
E541793
|
entity |
| Predicate | ametlikStaatusTaastatud |
P13710
|
FINISHED |
| Object | 1990. aastatel |
—
|
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: 1990. aastatel | Statement: [Eesti vapp, ametlikStaatusTaastatud, 1990. aastatel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ametlikStaatusTaastatud Context triple: [Eesti vapp, ametlikStaatusTaastatud, 1990. aastatel]
-
A.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
B.
associatedStatus
Indicates that one entity is linked to or characterized by a particular status or condition.
-
C.
statusSymbol
Indicates that something serves as a marker or representation of an entity’s social, economic, or cultural standing relative to others.
-
D.
laterStatus
chosen
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
E.
EstoniaStatus
Indicates the status or condition currently associated with Estonia in a given context.
- 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_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. |
Created at: April 16, 2026, 7:55 p.m.