Triple
T19173748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LIU Sharks wrestling program |
E469389
|
entity |
| Predicate | homeDualMeetType |
P65020
|
FINISHED |
| Object | indoor arena |
—
|
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: indoor arena | Statement: [LIU Sharks wrestling program, homeDualMeetType, indoor arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeDualMeetType Context triple: [LIU Sharks wrestling program, homeDualMeetType, indoor arena]
-
A.
doubleheaderType
Indicates the specific kind or classification of a doubleheader event or occurrence within a given context.
-
B.
meetsBetween
Indicates that one entity meets or encounters another at some point between two specified reference points or times.
-
C.
conferenceMatchupType
Indicates the type or category of matchup between entities within a conference context (e.g., intra-conference vs. inter-conference).
-
D.
homeMatchType
chosen
Indicates the type or category of match in which an entity is designated as the home side.
-
E.
dualPair
Indicates that two entities form a dual pair, standing in a mathematically defined dual relationship where each is the dual counterpart of the other.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f16613dc8190987c2d79dc616e40 |
completed | April 20, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.