Triple
T6341148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brown Bears |
E142627
|
entity |
| Predicate | sailingStatus |
P70077
|
FINISHED |
| Object | varsity sport |
—
|
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: varsity sport | Statement: [Brown Bears, sailingStatus, varsity sport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sailingStatus Context triple: [Brown Bears, sailingStatus, varsity sport]
-
A.
sailingUnder
Indicates that one entity (typically a vessel) is operating or traveling while registered, flagged, or officially recognized under the authority or jurisdiction of another entity (such as a country or organization).
-
B.
sailPlan
Indicates a plan or arrangement for how a vessel will be sailed, including intended route, timing, and sailing configuration.
-
C.
sailNumber
Indicates the identifying number assigned to a specific sail or sailing vessel, typically used to distinguish it from others.
-
D.
sailingVenue
Indicates the location or facility where sailing activities or events take place.
-
E.
sailingClass
Indicates that one entity is a type or category of sailing activity, vessel, or competition class to which the other entity belongs or is associated.
- 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_69c008d5ab108190b346c465696824a9 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0674311388190bb069a07a7ff60ef |
completed | March 22, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69c060ea1a988190889e47b7e0c819b8 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623bb29081908bfdfb84a07ece90 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:30 p.m.