Triple
T3601107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivy League women’s lacrosse |
E76256
|
entity |
| Predicate | goalOfGame |
P46673
|
FINISHED |
| Object | score more goals than opponent |
—
|
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: score more goals than opponent | Statement: [Ivy League women’s lacrosse, goalOfGame, score more goals than opponent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalOfGame Context triple: [Ivy League women’s lacrosse, goalOfGame, score more goals than opponent]
-
A.
competitionGoal
chosen
Indicates that one entity’s objective or desired outcome is defined in the context of a competition involving another entity.
-
B.
laterGoal
Indicates that one goal occurs or is intended to be achieved after another goal in time.
-
C.
opponentObjective
Indicates that one entity is the target or goal that an opposing entity aims to counter, defeat, or prevent from succeeding.
-
D.
statedAsGoalFor
Indicates that something has been explicitly declared or identified as a goal for a particular entity or context.
-
E.
gameWinningKicker
Indicates that an entity serves as the kicker responsible for securing the decisive, game-winning score in a contest.
- 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_69ad85d93dcc819094fba90cf70f4996 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc1a1e8c48190a28ea3ddfe8c4e54 |
completed | March 8, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69adb83b66708190bb9d2f23d6fd308e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.