Triple
T4975171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fourth Division |
E111746
|
entity |
| Predicate | promotionPlacesTypical |
P41169
|
FINISHED |
| Object | four clubs promoted |
—
|
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: four clubs promoted | Statement: [Fourth Division, promotionPlacesTypical, four clubs promoted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionPlacesTypical Context triple: [Fourth Division, promotionPlacesTypical, four clubs promoted]
-
A.
promotionPlaces
chosen
Indicates that one entity designates or assigns another entity to a higher position, rank, or status within some organizational or hierarchical structure.
-
B.
placesWithin
Indicates that one place or area is located entirely inside the boundaries of another place or area.
-
C.
typicalVenues
Indicates that the specified locations are common or standard places where the associated activity, event, or entity usually occurs or is hosted.
-
D.
placeType
Indicates the type or category of place associated with an entity (e.g., city, park, building).
-
E.
offersDayPlacesTo
Indicates that one entity provides or makes available daytime places or slots to another entity.
- 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_69bd441a0eb481908050fa4273b19eae |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd7146e6e881908a55ab2756b631f6 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:33 p.m.