Triple
T8924263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caesarian faction |
E212500
|
entity |
| Predicate | hasBaseOfSupport |
P60747
|
FINISHED |
| Object | veteran 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: veteran soldiers | Statement: [Caesarian faction, hasBaseOfSupport, veteran soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaseOfSupport Context triple: [Caesarian faction, hasBaseOfSupport, veteran soldiers]
-
A.
hasSupportBaseIn
Indicates that one entity maintains an operational or organizational base of support located in another entity.
-
B.
hasStand
Indicates that an entity possesses, is equipped with, or is supported by a stand or base structure.
-
C.
hasSupportBase
Indicates that one entity serves as the supporting base or foundation upon which another entity rests, is mounted, or is structurally stabilized.
-
D.
standingBasis
Indicates that one entity serves as the foundational reason, justification, or basis for another entity’s standing, status, or position in a given context.
-
E.
supportingBody
chosen
Indicates that one entity serves as a supporting or backing body for another entity, providing endorsement, resources, or structural support.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66547de881909ea9bfd104b32893 |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:57 p.m.