Triple
T958156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Courtroom 600 |
E20669
|
entity |
| Predicate | startUseForIMT |
P21846
|
FINISHED |
| Object | 1945 |
—
|
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: 1945 | Statement: [Courtroom 600, startUseForIMT, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startUseForIMT Context triple: [Courtroom 600, startUseForIMT, 1945]
-
A.
usesIntervention
Indicates that one entity applies, employs, or relies on a specific intervention (such as a treatment, method, or strategy) in relation to another entity or context.
-
B.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
C.
usesInfrastructure
Indicates that one entity makes use of, depends on, or operates through the infrastructure provided or managed by another entity.
-
D.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
E.
usedCapability
Indicates that an entity employed or exercised a particular capability, skill, or function in performing an action or achieving a result.
- 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_69a493b21f2881908132dcf45dcd2f36 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3fc94ec8190b55c6cdf3a37d6b5 |
completed | March 1, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a18ecc8190883f6206fe3b0fb6 |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b326d9d88190913c1a892a795707 |
completed | March 1, 2026, 9:44 p.m. |
Created at: March 1, 2026, 7:40 p.m.