Triple
T6365905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carli Lloyd |
E143227
|
entity |
| Predicate | scoredHatTrickIn |
P57817
|
FINISHED |
| Object | 2015 FIFA Women’s World Cup Final vs Japan |
—
|
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: 2015 FIFA Women’s World Cup Final vs Japan | Statement: [Carli Lloyd, scoredHatTrickIn, 2015 FIFA Women’s World Cup Final vs Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoredHatTrickIn Context triple: [Carli Lloyd, scoredHatTrickIn, 2015 FIFA Women’s World Cup Final vs Japan]
-
A.
scoredFor
Indicates that one entity achieved points or a score on behalf of another entity, such as a player scoring for a team.
-
B.
hasScoredFor
Indicates that one entity has scored points, goals, or similar achievements on behalf of another entity, such as a team, organization, or side.
-
C.
scoredInMatch
Indicates that an entity (typically a player or team) scored during a particular match.
-
D.
scoredInEvent
Indicates that an entity achieved a score or result within a specific event or competition.
-
E.
worldCupHatTricks
chosen
Indicates that a player has scored three or more goals in a single FIFA World Cup match.
- 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_69c008d8c61081908bcaf61510d881ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c068106e18819087ed2e9841d2b365 |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:32 p.m.