Triple
T16812886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princeton HWT |
E408658
|
entity |
| Predicate | primaryCompetitionContext |
P16079
|
FINISHED |
| Object | U.S. collegiate rowing |
—
|
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: U.S. collegiate rowing | Statement: [Princeton HWT, primaryCompetitionContext, U.S. collegiate rowing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCompetitionContext Context triple: [Princeton HWT, primaryCompetitionContext, U.S. collegiate rowing]
-
A.
primaryCompetition
Indicates that one entity is the main or most significant competitor of another within a given market, domain, or context.
-
B.
primaryCompetitionLevel
Indicates the main or highest level of competition at which an entity primarily competes or operates.
-
C.
secondaryCompetition
Indicates that one entity participates in or is involved with a secondary or subordinate competition relative to a primary one.
-
D.
competitiveContext
chosen
Indicates a situation in which entities are engaged in or influenced by competition with one another.
-
E.
primaryCompetitionCountry
Indicates the main country in which an entity primarily conducts or participates in competitive activities or markets.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2df5c888190a462614e1432c357 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.