Triple
T15346585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolokotronis |
E366936
|
entity |
| Predicate | relatedFieldOfNotability |
P39276
|
FINISHED |
| Object | military history of Greece |
—
|
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: military history of Greece | Statement: [Kolokotronis, relatedFieldOfNotability, military history of Greece]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedFieldOfNotability Context triple: [Kolokotronis, relatedFieldOfNotability, military history of Greece]
-
A.
notableField
chosen
Indicates the field, discipline, or area of activity for which an entity is especially known or distinguished.
-
B.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
C.
notableRelatedList
Indicates that there exists a curated or recognized list that is notably related to the subject, typically grouping it with similar or thematically connected entities.
-
D.
subjectNotableFor
Indicates that the subject is especially recognized or distinguished for a particular attribute, achievement, role, or characteristic.
-
E.
hasNamesakeNotability
Indicates that one entity is notable or recognized specifically because it shares the same name as another entity.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e1749bc8190a8b9cbcb27288a5b |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.