Triple
T38085832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Echigo |
E950973
|
entity |
| Predicate | associatedMilitaryProwess |
P7256
|
FINISHED |
| Object | battlefield tactics |
—
|
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: battlefield tactics | Statement: [Lord of Echigo, associatedMilitaryProwess, battlefield tactics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedMilitaryProwess Context triple: [Lord of Echigo, associatedMilitaryProwess, battlefield tactics]
-
A.
hasMilitaryAssociation
Indicates a relationship in which an entity is connected or affiliated with a military organization, activity, or function.
-
B.
militaryReputation
Indicates the perceived standing or esteem of an entity based on its past or present military performance, conduct, or capabilities.
-
C.
militaryCharacteristic
chosen
Indicates that one entity possesses a specific military-related attribute, quality, or feature in relation to another entity or context.
-
D.
hadMilitaryFollowing
Indicates that an entity was supported or backed by a group of military personnel or forces.
-
E.
associatedWithWar
Indicates a relationship where an entity is connected or related to war, such as by involvement, influence, cause, or context.
- 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.