Triple
T7256662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NWSL regular season |
E157738
|
entity |
| Predicate | isPrimaryPhaseOf |
P7628
|
FINISHED |
| Object | NWSL league competition |
—
|
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: NWSL league competition | Statement: [NWSL regular season, isPrimaryPhaseOf, NWSL league competition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryPhaseOf Context triple: [NWSL regular season, isPrimaryPhaseOf, NWSL league competition]
-
A.
mainPhase
chosen
Indicates that an event, action, or state occurs during the primary or central phase of a larger process or sequence.
-
B.
hasEarlierPhase
Indicates that one phase occurs before another phase in a process or sequence.
-
C.
majorPhase
Indicates that one phase is a primary or dominant stage within a larger process, lifecycle, or sequence.
-
D.
targetsPhase
Indicates that an action, process, or entity is specifically directed toward or intended to affect a particular phase or stage within a larger sequence or lifecycle.
-
E.
hasPhaseRelation
Indicates that two entities are related by a specific phase difference or phase alignment in time or a cyclical process.
- 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_69c6882d81d4819085f7ff862951ee4f |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6eaa274bc8190b017b71583711453 |
completed | March 27, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69c6e7666ffc81908bf643d8257e6337 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:57 p.m.