Triple
T25511410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love in the Afternoon |
E639388
|
entity |
| Predicate | languageVersionTitle |
P176684
|
FINISHED |
| Object | Ariane |
—
|
NE NERFINISHED |
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: Ariane | Statement: [Love in the Afternoon, languageVersionTitle, Ariane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageVersionTitle Context triple: [Love in the Afternoon, languageVersionTitle, Ariane]
-
A.
languageVersions
Indicates a relationship where one entity represents a specific version or variant of a language associated with another entity.
-
B.
officialLanguageVersion
Indicates that one language variant is the officially recognized form or version used for formal or administrative purposes in relation to another language or context.
-
C.
primaryLanguageVersion
Indicates that one language version of a resource is designated as the main or default version among its language variants.
-
D.
supportsLanguageVersion
Indicates that one entity provides compatibility with, or can correctly operate using, a specified version of a language.
-
E.
languageLevel
Indicates the proficiency or complexity level of a language associated with an entity.
- 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e60109648190947a64ca4ce81a3a |
completed | May 3, 2026, 6:06 a.m. |
Created at: April 21, 2026, 2:49 p.m.