Triple
T1141259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida Complex League |
E23455
|
entity |
| Predicate | rosterType |
P6625
|
FINISHED |
| Object | primarily first-year professional 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: primarily first-year professional players | Statement: [Florida Complex League, rosterType, primarily first-year professional players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rosterType Context triple: [Florida Complex League, rosterType, primarily first-year professional players]
-
A.
rosterSize
Indicates the total number of individuals included on a given roster.
-
B.
typeOfTeams
Indicates the categories or kinds of teams to which an entity or group of entities belongs.
-
C.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
D.
typicalRosterSource
chosen
Indicates that one entity is the usual or standard source from which the other entity’s roster or list of members is derived.
-
E.
personnelType
Indicates the classification or role category assigned to a person within an organization or system.
- 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc290ae08190afbf7e7ea2100d9e |
completed | March 1, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4d4104819084027a043c6118cb |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.