Triple
T3716011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Provost Marshal (RAF) |
E81531
|
entity |
| Predicate | useOfLanguage |
P18209
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Provost Marshal (RAF), useOfLanguage, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useOfLanguage Context triple: [Provost Marshal (RAF), useOfLanguage, English]
-
A.
languageUse
chosen
Indicates the language or languages an entity uses for communication, expression, or interaction.
-
B.
usedInLanguage
Indicates that something (such as a word, expression, or symbol) is employed or occurs within a particular language.
-
C.
languageOfExpression
Indicates that a particular language is used as the medium or form in which an expression (such as a text, utterance, or work) is realized.
-
D.
usesWorkingLanguagesOf
Indicates that one entity employs or operates using the working languages associated with another entity.
-
E.
officialLanguageUse
Indicates that a particular language is formally designated and used by an authority (such as a government or institution) for official communication, documentation, or functions.
- 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_69ad8b1a81588190b3f27a5483bb610e |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc9cf77dc819098979094172d82d1 |
completed | March 8, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69adc0436e508190909ec4a3e8443aef |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:33 p.m.