Triple
T15732453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sphacteria campaign |
E381375
|
entity |
| Predicate | capturedForceSize |
P119975
|
FINISHED |
| Object | over 100 Spartan citizens |
—
|
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: over 100 Spartan citizens | Statement: [Sphacteria campaign, capturedForceSize, over 100 Spartan citizens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capturedForceSize Context triple: [Sphacteria campaign, capturedForceSize, over 100 Spartan citizens]
-
A.
capturedForce
Indicates that one entity has taken control of another entity or group through force, restraint, or coercive action.
-
B.
hasApproximateDefendingForceSize
Indicates that an entity is associated with a defending force whose size is known only approximately rather than as an exact value.
-
C.
primaryOpposingForceSize
Indicates the size or magnitude of the main opposing force acting against a subject in a given context.
-
D.
attackingForceApprox
Indicates that one entity is the approximate attacking force, in terms of size or strength, relative to another entity or context.
-
E.
commandingForce2Strength
Indicates that a commanding force possesses or exerts a particular level or measure of strength.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fd3614481908b2694b1d3550058 |
completed | April 16, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e0094af5b481908ad51d5d7ba0c726 |
completed | April 15, 2026, 9:55 p.m. |
Created at: April 10, 2026, 4:46 a.m.