Triple
T32769925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aux quatre coins du monde |
E838022
|
entity |
| Predicate | hasIntrospectiveStyle |
P115086
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Aux quatre coins du monde, hasIntrospectiveStyle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntrospectiveStyle Context triple: [Aux quatre coins du monde, hasIntrospectiveStyle, true]
-
A.
hasIntrospectiveTone
chosen
Indicates that the subject expresses thoughts, feelings, or experiences in a reflective, inward-looking manner.
-
B.
hasInterpretationStyle
Indicates a relationship where an entity is associated with a particular manner, method, or style in which it is interpreted or understood.
-
C.
supportsIntrospectionOf
Indicates that one entity enables or facilitates the examination or analysis of the internal state, structure, or behavior of another entity.
-
D.
hasStructuralStyle
Indicates that one entity possesses, exhibits, or is characterized by a particular architectural or structural design style.
-
E.
hasStyle
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
- 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffac35ac5481908b6bdfd5bbe8c76e |
completed | May 9, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69ffabbfd2548190964c851496bbbaee |
completed | May 9, 2026, 9:48 p.m. |
Created at: May 1, 2026, 1:13 a.m.