Triple
T23489826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | district court-martial |
E570637
|
entity |
| Predicate | mayBeConvenedIn |
P30361
|
FINISHED |
| Object | field conditions |
—
|
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: field conditions | Statement: [district court-martial, mayBeConvenedIn, field conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeConvenedIn Context triple: [district court-martial, mayBeConvenedIn, field conditions]
-
A.
convenedFor
Indicates that an event, meeting, or gathering was brought together for a specific purpose, topic, or beneficiary.
-
B.
convenedIn
Indicates that an event, meeting, or formal gathering was brought together and held at a specific location.
-
C.
convenesIn
Indicates that an entity brings together or assembles a group, meeting, or event at a specific place or venue.
-
D.
convenesOn
Indicates that an event, group, or body holds a meeting or session at a specific time or date.
-
E.
conveningCondition
chosen
Indicates the circumstances or requirements under which a meeting, gathering, or formal session is initiated or brought together.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7dba7388190a322ab059bb6522a |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:04 p.m.