Triple
T34648980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Florida Ospreys athletic uniform |
E889780
|
entity |
| Predicate | hasNumberPlacement |
P197964
|
FINISHED |
| Object | front of jersey |
—
|
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: front of jersey | Statement: [North Florida Ospreys athletic uniform, hasNumberPlacement, front of jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberPlacement Context triple: [North Florida Ospreys athletic uniform, hasNumberPlacement, front of jersey]
-
A.
positionOnNumbers
Indicates a relationship where one entity occupies a specific numerical position or rank relative to others in an ordered sequence of numbers.
-
B.
hasNumberAtPeak
Indicates that an entity possesses a specific numerical value measured at its highest or peak point.
-
C.
hasNumeral
Indicates that one entity is associated with a numeral representation or numeric symbol of another entity.
-
D.
numberOfPlacements
Indicates the total count of times an entity has been placed or assigned within a given context or system.
-
E.
isNumbered
Indicates that an entity has been assigned a specific number or position in an ordered sequence.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69febce5877c8190a5e000ef5331ec88 |
completed | May 9, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69febad1cd588190abc7686bcb39a371 |
completed | May 9, 2026, 4:40 a.m. |
| PDg | Predicate description generation | batch_69febce420b081908e1c052751a22b1f |
completed | May 9, 2026, 4:49 a.m. |
Created at: May 1, 2026, 2:04 a.m.