Triple
T6611102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FA Women's Cup |
E149238
|
entity |
| Predicate | mergerIntoFA |
P77
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [FA Women's Cup, mergerIntoFA, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergerIntoFA Context triple: [FA Women's Cup, mergerIntoFA, 1993]
-
A.
mergedInto
chosen
Indicates that one entity has been combined with and absorbed into another entity, ceasing to exist as a separate unit.
-
B.
mergerResult
Indicates that one or more entities have combined into a single entity, specifying the outcome or resulting entity of the merger.
-
C.
mergerLocation
Indicates the place or venue where a merger between entities occurs or is formally executed.
-
D.
mergedBy
Indicates that one entity is combined or integrated into another entity through the action or decision of a specific agent.
-
E.
mergerResultedIn
Indicates that a merger between entities led to the creation, change, or outcome represented by the related entity or state.
- 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_69c687ebc680819094caf71faba2efe2 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cf3796d08190a26e988386089447 |
completed | March 27, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69c6acfed25481909cac74c84a9fe088 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:57 p.m.