Triple
T36935568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2001–02 NPSL Championship |
E913604
|
entity |
| Predicate | titleCapturedBy |
P34204
|
FINISHED |
| Object | Philadelphia KiXX |
—
|
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: Philadelphia KiXX | Statement: [2001–02 NPSL Championship, titleCapturedBy, Philadelphia KiXX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleCapturedBy Context triple: [2001–02 NPSL Championship, titleCapturedBy, Philadelphia KiXX]
-
A.
capturedTitleFrom
Indicates that one entity has taken possession or control of another entity’s title or designation from a source entity.
-
B.
capturedBy
Indicates that one entity has been seized, taken into control, or otherwise apprehended by another entity.
-
C.
titleAcquiredBy
chosen
Indicates that a particular title, rank, or designation has been obtained or earned by a specific entity.
-
D.
titleThrough
Indicates a relationship where one entity holds or is identified by a specific title by means of, or via the mediation of, another entity or context.
-
E.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title associated with another entity.
- 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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffc89596d08190b97bd60b45c7f9c0 |
completed | May 9, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69ffc81ba5dc8190ae94d44e2284948f |
completed | May 9, 2026, 11:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.