Triple
T16230092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cavalry |
E393954
|
entity |
| Predicate | modernMeaningIncludes |
P102770
|
FINISHED |
| Object | armored units |
—
|
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: armored units | Statement: [Cavalry, modernMeaningIncludes, armored units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernMeaningIncludes Context triple: [Cavalry, modernMeaningIncludes, armored units]
-
A.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
-
B.
textMeaning
Indicates that one text expresses, conveys, or corresponds to a particular meaning or semantic content.
-
C.
possibleMeaning
Indicates that something may plausibly represent, signify, or be interpreted as a particular meaning or sense.
-
D.
meaningInContext
chosen
Indicates that one entity represents or conveys a particular meaning, interpretation, or sense within a specific context or situation.
-
E.
stringMeaning
Indicates that one entity represents the semantic content or interpretation of a given string associated with another entity.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e23d29438c81909aa2724cc47bb959 |
completed | April 17, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.