Triple
T33800328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Class C mandate |
E866196
|
entity |
| Predicate | languageUsedInInstruments |
P201917
|
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: [Class C mandate, languageUsedInInstruments, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedInInstruments Context triple: [Class C mandate, languageUsedInInstruments, English]
-
A.
instrumentsUsedBy
Indicates that a particular instrument, tool, or device is employed or utilized by a given entity to perform an action or achieve a result.
-
B.
usedAsInstrumentBy
Indicates that one entity functions as a tool, means, or instrument through which another entity performs an action or achieves an effect.
-
C.
instruments
Indicates that an agent uses a tool, device, or means to carry out an action or achieve an effect.
-
D.
materialUsedForInstruments
Indicates that a particular material is used in the construction or manufacture of one or more instruments.
-
E.
programmingInstrument
Indicates that an entity uses a particular instrument, tool, or device to perform a programming-related action or task.
- F. None of above. chosen
Provenance (4 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0031ed5d708190ab93516ad081ada6 |
completed | May 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_6a0031b5dbd081908eb0f4dbb8a0eac3 |
completed | May 10, 2026, 7:20 a.m. |
| PDg | Predicate description generation | batch_6a0031ec758c81908a3877bc19ce2701 |
completed | May 10, 2026, 7:21 a.m. |
Created at: May 1, 2026, 1:46 a.m.