Triple
T3547757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USL League Two |
E75036
|
entity |
| Predicate | playerPathway |
P18155
|
FINISHED |
| Object | path to USL Championship |
—
|
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: path to USL Championship | Statement: [USL League Two, playerPathway, path to USL Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerPathway Context triple: [USL League Two, playerPathway, path to USL Championship]
-
A.
hasPlayerPathway
chosen
Indicates that there is a defined developmental or progression route available for a player within a given context or system.
-
B.
developmentPathwayFor
Indicates that one entity serves as a route, mechanism, or process through which the development or progression of another entity occurs.
-
C.
careerPath
Indicates the progression or sequence of roles, positions, or occupations that an individual follows over time in their professional life.
-
D.
offersPathway
Indicates that one entity provides a route, means, or opportunity for another entity to reach, access, or transition to something.
-
E.
careerSystem
Indicates a relationship where an entity is part of, governed by, or operates within a particular career-related system or framework.
- 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.