Triple
T25666163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sky Blue Soccer |
E643521
|
entity |
| Predicate | notableFormerAssetName |
P193818
|
FINISHED |
| Object | Sky Blue FC |
—
|
NE NERFINISHED |
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: Sky Blue FC | Statement: [Sky Blue Soccer, notableFormerAssetName, Sky Blue FC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFormerAssetName Context triple: [Sky Blue Soccer, notableFormerAssetName, Sky Blue FC]
-
A.
notableAsset
Indicates that an entity possesses or is associated with an asset that is particularly significant, prominent, or noteworthy in relation to it.
-
B.
notableFormerConstructor
Indicates that an entity was previously a constructor (e.g., team or organization) associated with another entity in a way considered notable or significant.
-
C.
notableFormerHolderRole
Indicates that an entity previously held a particular notable role or position.
-
D.
notableAlternateHolder
Indicates that an entity is recognized as a significant or noteworthy alternative holder or bearer of something typically associated with another primary holder.
-
E.
notableForbesListing
Indicates that an entity has been recognized or included in a notable Forbes magazine list or ranking.
- 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_69e77e7e45648190a068ed3faa8016ea |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
| PDg | Predicate description generation | batch_69fd57b9cdec81908536c4159e375931 |
completed | May 8, 2026, 3:25 a.m. |
Created at: April 21, 2026, 7:04 p.m.