Triple
T3547731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USL League Two |
E75036
|
entity |
| Predicate | playerBase |
P13613
|
FINISHED |
| Object | college players |
—
|
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: college players | Statement: [USL League Two, playerBase, college players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerBase Context triple: [USL League Two, playerBase, college players]
-
A.
player
Indicates that an entity participates in a game, sport, or activity in the role of a player.
-
B.
featuresPlayer
Indicates that something includes or prominently presents a particular player as part of its content or composition.
-
C.
userBase
Indicates that one entity serves as the primary or foundational group of users associated with another entity.
-
D.
typicalPlayerProfile
chosen
Indicates the usual or characteristic attributes, behaviors, or demographics associated with a representative player in a given context.
-
E.
trainingBase
Indicates that one entity serves as the training base, site, or facility where another entity receives training or instruction.
- 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbfd0eb6081908f1380db4cfade87 |
completed | March 8, 2026, 6:28 p.m. |
| PD | Predicate disambiguation | batch_69adb83270ac819083967db0570167d2 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:20 p.m.