Triple
T37013411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seattle Regional 4 |
E916009
|
entity |
| Predicate | advancementOutcome |
P59870
|
FINISHED |
| Object | produced one Final Four qualifier |
—
|
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: produced one Final Four qualifier | Statement: [Seattle Regional 4, advancementOutcome, produced one Final Four qualifier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advancementOutcome Context triple: [Seattle Regional 4, advancementOutcome, produced one Final Four qualifier]
-
A.
advancementStatus
Indicates the current stage or progress state of an ongoing process, project, or development.
-
B.
advancementControl
Indicates a relationship where one entity directs, manages, or regulates the progress or forward movement of another entity or process.
-
C.
achievementStatus
Indicates the current state or level of completion of an achievement-related goal or milestone for an entity.
-
D.
outcomeOf
chosen
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
E.
programOutcome
Indicates the resulting state, effect, or consequence produced by executing or completing a program.
- 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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.