Triple
T9289821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Diego Seals |
E223487
|
entity |
| Predicate | usesLacrosseFormat |
P87451
|
FINISHED |
| Object | box lacrosse rules |
—
|
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: box lacrosse rules | Statement: [San Diego Seals, usesLacrosseFormat, box lacrosse rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLacrosseFormat Context triple: [San Diego Seals, usesLacrosseFormat, box lacrosse rules]
-
A.
homeVenueLacrosse
Indicates that a specified venue serves as the designated home location where a particular lacrosse team hosts its home games or matches.
-
B.
usesAmericanRules
Indicates that the action, process, or system is conducted according to American rules or standards rather than other rule sets.
-
C.
usesNumberOfPlayersOnFieldPerTeam
Indicates that the relationship specifies or depends on how many players each team has on the field at a given time.
-
D.
usesNCAARules
Indicates that one entity applies or follows NCAA rules in its activities, operations, or decision-making.
-
E.
playsOnRinkType
Indicates that an entity participates in a game or activity on a specific type of rink surface or rink configuration.
- F. None of above. chosen
Provenance (4 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd08643a848190a8b5be1ccc0b2ef6 |
completed | April 1, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:35 p.m.