Triple
T34913747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltic peoples |
E1006944
|
entity |
| Predicate | modernRepresentative |
P193327
|
FINISHED |
| Object | Latvians |
—
|
NE NERFINISHED |
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: Latvians | Statement: [Baltic peoples, modernRepresentative, Latvians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernRepresentative Context triple: [Baltic peoples, modernRepresentative, Latvians]
-
A.
earlyRepresentative
Indicates that one entity serves as an initial or pioneering representative or example of another entity in time or development.
-
B.
majorRepresentative
Indicates that one entity serves as the primary or main representative of another entity.
-
C.
representative
Indicates that one entity serves as an official agent or spokesperson acting on behalf of another entity.
-
D.
historicalRepresentative
Indicates that one entity serves or served as an official representative or delegate of another entity in a historical context.
-
E.
confederationRepresentative
Indicates that one entity serves as an official representative or delegate of a confederation in relation to 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
| PDg | Predicate description generation | batch_69fd4128ed908190837ec9936774a1cf |
completed | May 8, 2026, 1:49 a.m. |
Created at: May 3, 2026, 4 p.m.