Triple
T21659536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sorcerer |
E534556
|
entity |
| Predicate | supportsTextOutput |
P114071
|
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: [Sorcerer, supportsTextOutput, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTextOutput Context triple: [Sorcerer, supportsTextOutput, yes]
-
A.
supportsTextFormat
Indicates that one entity is capable of handling, rendering, or otherwise working with a specified text format.
-
B.
supportsOutputType
chosen
Indicates that one entity is capable of producing, handling, or generating data or results of the specified output type.
-
C.
outputIs
Indicates that one entity functions as the result, product, or outcome produced by another entity or process.
-
D.
usesTextService
Indicates that an entity makes use of a text-based service to perform some function or obtain some benefit.
-
E.
supportsNarrativeText
Indicates that one entity provides justification, evidence, or contextual backing that helps explain or validate the narrative content expressed 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_69e0c467e1f48190af2650b19175abc4 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef6c06844c81909b9c91e02fa4e6e1 |
completed | April 27, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:36 p.m.