Triple
T16561597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Classicissima |
E402350
|
entity |
| Predicate | hasInternationalField |
P124059
|
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: [La Classicissima, hasInternationalField, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInternationalField Context triple: [La Classicissima, hasInternationalField, yes]
-
A.
hasInternationalStatus
Indicates that an entity holds a recognized status, role, or standing at the international level rather than being limited to a single country or local jurisdiction.
-
B.
hasInternationalDistrict
Indicates that an entity possesses, contains, or is associated with a designated international district within its boundaries or scope.
-
C.
isInternational
Indicates that something has a connection to, involves, or extends across more than one country.
-
D.
hasInternationalService
Indicates that an entity provides or is connected to transportation or communication services that operate across national borders.
-
E.
hasInternationalDestinationType
Indicates that something is associated with a type or category of international destination.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3576eb63081908cb5dc6c0a8a13ac |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:15 a.m.