Triple
T38186070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quake III Arena |
E1005317
|
entity |
| Predicate | renderingFeature |
P81690
|
FINISHED |
| Object | curved surfaces |
—
|
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: curved surfaces | Statement: [Quake III Arena, renderingFeature, curved surfaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renderingFeature Context triple: [Quake III Arena, renderingFeature, curved surfaces]
-
A.
renderingMode
Indicates the specific way in which content or graphics are processed and displayed (e.g., style, technique, or pipeline used for rendering).
-
B.
displaysFeature
Indicates that one entity presents, shows, or makes visible a particular feature or characteristic of another entity.
-
C.
renderingTechnology
chosen
Indicates the graphics or visualization method used to generate the visual representation of an object, scene, or interface.
-
D.
documentedFeature
Indicates that a feature has been formally recorded or described in documentation.
-
E.
markingFeature
Indicates a feature that serves as a distinguishing mark or identifier associated with an 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:29 p.m.