Triple
T32682314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philip Johnston |
E835619
|
entity |
| Predicate | usedLanguageAs |
P101866
|
FINISHED |
| Object | military code |
—
|
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: military code | Statement: [Philip Johnston, usedLanguageAs, military code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedLanguageAs Context triple: [Philip Johnston, usedLanguageAs, military code]
-
A.
usesLanguageAs
chosen
Indicates that one entity communicates or operates using another entity as its language or linguistic medium.
-
B.
usesLanguageFor
Indicates that an entity employs a particular language as a tool or medium to perform some activity, function, or purpose.
-
C.
usedInLanguage
Indicates that something (such as a word, expression, or symbol) is employed or occurs within a particular language.
-
D.
languageUsedAs
Indicates that one language is employed in a specific role, function, or context relative to another entity or situation.
-
E.
usedForLanguageSpokenIn
Indicates that something (such as a resource, tool, or medium) is used for expressing or communicating a language that is spoken in a particular place or region.
- 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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c7e92f38819084db3081ae5de9ec |
completed | May 3, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:09 a.m.