Triple
T16077812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan trial courts |
E390019
|
entity |
| Predicate | handlesStage |
P61192
|
FINISHED |
| Object | first instance in most cases |
—
|
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: first instance in most cases | Statement: [Michigan trial courts, handlesStage, first instance in most cases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesStage Context triple: [Michigan trial courts, handlesStage, first instance in most cases]
-
A.
setsStageFor
Indicates that one event, condition, or action creates the necessary circumstances or groundwork for another to occur.
-
B.
coreStageBehavior
Indicates the fundamental or default way an entity acts or responds in a given context or process.
-
C.
servesStage
chosen
Indicates that an entity functions as a stage or phase within a larger process, sequence, or workflow.
-
D.
hasStageType
Indicates that an entity is associated with, or classified by, a specific type or category of stage within a process, lifecycle, or workflow.
-
E.
supportsStageManager
Indicates that one entity provides compatibility or functionality required for another entity to use or run Stage Manager.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.