Triple
T24722673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Two Oak Ventures |
E612348
|
entity |
| Predicate | competitionLevelOfOwnedClub |
P157039
|
FINISHED |
| Object | top division of U.S. soccer |
—
|
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: top division of U.S. soccer | Statement: [Two Oak Ventures, competitionLevelOfOwnedClub, top division of U.S. soccer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionLevelOfOwnedClub Context triple: [Two Oak Ventures, competitionLevelOfOwnedClub, top division of U.S. soccer]
-
A.
supportsClubLeagueLevel
Indicates that an entity provides backing or resources enabling a club to participate at a specific league level.
-
B.
supportsLeagueClub
Indicates that one entity provides backing, assistance, or endorsement to a league-affiliated club.
-
C.
supportedClubLeague
Indicates that an entity (typically a person or group) actively supported a particular sports club participating in a specified league.
-
D.
supportsClubInLeague
Indicates that one entity provides backing or sponsorship for a club participating in a particular league.
-
E.
leagueOwned
Indicates that a league has ownership or controlling rights over the referenced entity.
- 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_69e2d7d6e7a48190bb43b0d8bb1137a0 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f410fc18808190b4e47d5a71d3a126 |
completed | May 1, 2026, 2:33 a.m. |
Created at: April 18, 2026, 3:41 a.m.