Triple
T21414640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern All-Stars |
E528267
|
entity |
| Predicate | hasCaptainsFormatParticipation |
P143873
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Eastern All-Stars, hasCaptainsFormatParticipation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCaptainsFormatParticipation Context triple: [Eastern All-Stars, hasCaptainsFormatParticipation, yes]
-
A.
isCaptainInLeague
Indicates that an entity serves as the captain of a team participating in a specified league.
-
B.
captainedFormat
Indicates that one entity served as the captain or leader in charge of another entity, typically a team, vessel, or organized group, during a specific event or period.
-
C.
captainedRepresentativeTeam
Indicates that an entity has served as the captain of a representative (e.g., national or regional) team.
-
D.
hasNotableCaptain
Indicates that an entity has a specific captain who is recognized as notable or distinguished in some way.
-
E.
servedAsCaptainFrom
Indicates that an entity held the role of captain of another entity starting from a specified point in time.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b2032fe48190907b282e2fffa2bd |
completed | April 22, 2026, 11:33 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 5:45 p.m.