Triple
T2372151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 NWSL Championship |
E46113
|
entity |
| Predicate | regulationTime |
P25687
|
FINISHED |
| Object | 90 minutes |
—
|
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: 90 minutes | Statement: [2014 NWSL Championship, regulationTime, 90 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulationTime Context triple: [2014 NWSL Championship, regulationTime, 90 minutes]
-
A.
regulatesTimeFor
Indicates that one entity controls, influences, or sets the timing or schedule of another entity’s activities or processes.
-
B.
regulationMinutes
chosen
Indicates the number of minutes played during the standard regulation period of a game, excluding any overtime or extra periods.
-
C.
regulationStatus
Indicates the regulatory condition or compliance state that applies to an entity under relevant rules or laws.
-
D.
allowsRegulationOf
Indicates that one entity grants the authority, means, or conditions for another entity to control, manage, or govern something.
-
E.
subjectToRegulation
Indicates that an entity is governed, constrained, or controlled by a specific rule, law, or regulatory framework.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc771302481908540e31abb5aeeba |
completed | March 7, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69abc59b88348190a2d6c08f69974117 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:56 p.m.