Triple
T38137333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Roanoke Island |
E952385
|
entity |
| Predicate | unionForcesStrength |
P65381
|
FINISHED |
| Object | approximately 10,000 soldiers |
—
|
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: approximately 10,000 soldiers | Statement: [Battle of Roanoke Island, unionForcesStrength, approximately 10,000 soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unionForcesStrength Context triple: [Battle of Roanoke Island, unionForcesStrength, approximately 10,000 soldiers]
-
A.
unionForces
Indicates that multiple forces are combined into a single, unified force acting together.
-
B.
unionForcesComposition
Indicates that multiple forces are combined or aggregated to form a single resultant force.
-
C.
UnionForcesStrength
chosen
Indicates the level or magnitude of military power possessed by Union forces in a given context.
-
D.
unionForcesCondition
Indicates a condition under which two or more parties agree to combine or coordinate their forces or efforts.
-
E.
unionStrength
Indicates the degree of solidarity, cohesion, or collective power within or among unions or union members.
- 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_69f76f09a7148190a4b91c0bacdc127a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.