Triple
T8887231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Section |
E211561
|
entity |
| Predicate | hadCounterpart |
P6587
|
FINISHED |
| Object | Navy Section |
—
|
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: Navy Section | Statement: [Army Section, hadCounterpart, Navy Section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadCounterpart Context triple: [Army Section, hadCounterpart, Navy Section]
-
A.
hasCounterpart
chosen
Indicates that one entity corresponds to, matches, or serves as an equivalent or parallel version of another entity.
-
B.
hadJudicialCounterpart
Indicates that one legal or judicial entity corresponded to, or was matched by, another entity serving an equivalent judicial role or function.
-
C.
counterpartService
Indicates that one service functions as the corresponding or matching service to another within a defined relationship or context.
-
D.
hadFort
Indicates that an entity possessed, controlled, or contained a fort at some time.
-
E.
isOppositionCounterpartOf
Indicates a relationship where one entity serves as the opposing or counterpart force, side, or position to another within a conflict, competition, or contrast.
- 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_69ca838f9e20819096ab1f236a70381a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc618d4c188190810d2e38591f515a |
completed | April 1, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2aec04819093c932fe51c0f08d |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:53 p.m.