Triple
T25285412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hammons Field |
E633922
|
entity |
| Predicate | hasFoulPoles |
P97140
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hammons Field, hasFoulPoles, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFoulPoles Context triple: [Hammons Field, hasFoulPoles, yes]
-
A.
hasFoulType
Indicates that an entity is associated with or characterized by a specific type or category of foul (e.g., in a game, sport, or rule system).
-
B.
hasPoleAt
chosen
Indicates that one entity possesses, contains, or is associated with a pole located at a specific point or position.
-
C.
foulsPenalizedBy
Indicates that a foul committed by one party is punished or sanctioned by another authority or rule-enforcing entity.
-
D.
hasDoublePoleAt
Indicates that a function or expression has a pole of order two (a second-order singularity) at a specified point.
-
E.
foulLimitPerTeam
Indicates the maximum number of fouls that a single team is allowed to commit within a defined game or competition context.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 1:19 p.m.