Triple
T3590119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Thermopylae |
E76004
|
entity |
| Predicate | forceSize |
P49546
|
FINISHED |
| Object | small Greek force |
—
|
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: small Greek force | Statement: [Battle of Thermopylae, forceSize, small Greek force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forceSize Context triple: [Battle of Thermopylae, forceSize, small Greek force]
-
A.
forceSizeUnion
Indicates that the combined size or extent of multiple entities is being constrained or determined as a single unified whole.
-
B.
forceType
Indicates the specific kind or category of force involved in an interaction or event (e.g., physical, legal, military, or other defined force classifications).
-
C.
forceDirection
Indicates the direction in which a force is applied or exerted in the relationship between entities.
-
D.
forceSizeConfederate
Indicates that one entity compels or influences another (the confederate) to adopt or present a particular physical size or size-related appearance.
-
E.
forceStructure
Indicates a relationship where one entity imposes or defines the structural arrangement, organization, or configuration of 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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc13c9514819096adf60b15016b8b |
completed | March 8, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69adb839b4e08190b1c0d611cccb11ae |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb902e61c81908f10494f828e260f |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:22 p.m.