Triple
T18443624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Crown |
E450597
|
entity |
| Predicate | visibleBestInMonth |
P131628
|
FINISHED |
| Object | August |
—
|
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: August | Statement: [Southern Crown, visibleBestInMonth, August]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibleBestInMonth Context triple: [Southern Crown, visibleBestInMonth, August]
-
A.
bestOf
Indicates that one entity is the top-ranked or most outstanding member within a specified group, set, or collection.
-
B.
bestObservedWith
Indicates that one entity is most effectively or appropriately observed, detected, or measured when used or considered together with another specified entity.
-
C.
featuredFor
Indicates that one entity is highlighted, promoted, or specially showcased in the context or for the benefit of another entity.
-
D.
monthOfMainLanding
Indicates the calendar month in which the primary or main landing event takes place.
-
E.
bestVisitedBy
Indicates that an entity is most suitably or optimally accessed, experienced, or reached by using a particular mode, route, or means of visiting.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c12a0248190a848a1fe833a1975 |
completed | April 19, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:30 a.m.