Triple
T35422532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special World |
E1023831
|
entity |
| Predicate | finalLevel |
P197715
|
FINISHED |
| Object | Funky |
—
|
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: Funky | Statement: [Special World, finalLevel, Funky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalLevel Context triple: [Special World, finalLevel, Funky]
-
A.
finalLevelType
Indicates the type or category assigned to the final level or stage of a process, system, or hierarchy.
-
B.
finalPhaseOf
Indicates that one process, stage, or event constitutes the concluding or last phase of another broader process or sequence.
-
C.
finalService
Indicates that a service represents the last or concluding service in a sequence, process, or lifecycle.
-
D.
finalValue
Indicates the resulting or ultimate value obtained after all relevant operations, changes, or calculations have been completed.
-
E.
frontLevel
Indicates a relationship where one entity is positioned at or aligned with the foremost or leading level relative to another reference point or structure.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fea2d0a4d08190aa06aeb902a02d5a |
completed | May 9, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fea24698348190b9b992a8e7cdbcd0 |
completed | May 9, 2026, 2:56 a.m. |
| PDg | Predicate description generation | batch_69fea2cfcd648190a15e5b90889095b1 |
completed | May 9, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4:03 p.m.