Triple
T14494005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fosse Dionne |
E359441
|
entity |
| Predicate | isEnigmatic |
P22515
|
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: [Fosse Dionne, isEnigmatic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEnigmatic Context triple: [Fosse Dionne, isEnigmatic, true]
-
A.
hasEnigmaticCharacter
chosen
Indicates that something possesses a mysterious, puzzling, or difficult-to-interpret quality or nature.
-
B.
isUndeciphered
Indicates that something has not yet been successfully interpreted, decoded, or understood in terms of its meaning or structure.
-
C.
hasMystery
Indicates that one entity possesses, contains, or is associated with something unknown, secret, or unexplained in relation to another entity.
-
D.
isCruxOf
Indicates that something is the central, most critical, or decisive element within a situation, argument, or problem.
-
E.
isAbout
Indicates that one entity has as its subject, focus, or primary concern the content, topic, or theme represented by 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de930f34d08190b4b30e54e2f702ed |
completed | April 14, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:21 a.m.