Triple
T24381927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gadites |
E614633
|
entity |
| Predicate | militaryDescription |
P7256
|
FINISHED |
| Object | mighty men of valor |
—
|
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: mighty men of valor | Statement: [Gadites, militaryDescription, mighty men of valor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryDescription Context triple: [Gadites, militaryDescription, mighty men of valor]
-
A.
militaryCharacteristic
chosen
Indicates that one entity possesses a specific military-related attribute, quality, or feature in relation to another entity or context.
-
B.
militarySection
Indicates that one entity is a specific branch, division, or section within a larger military organization or force.
-
C.
militaryFunction
Indicates a relationship where an entity serves a specific role, duty, or operational purpose within a military context.
-
D.
militaryDomain
Indicates that the relationship or action occurs within, pertains to, or is specifically associated with the military sphere or context.
-
E.
militarySystem
Indicates a relationship where an entity functions as, belongs to, or is characterized by a particular military organizational or operational system.
- 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293dc0c3c8190ad6de5db50ccbd76 |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:03 a.m.