Triple
T37449316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ScreenX multi‑projection system |
E930634
|
entity |
| Predicate | projectionCoverage |
P187828
|
FINISHED |
| Object | up to 270 degrees |
—
|
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: up to 270 degrees | Statement: [ScreenX multi‑projection system, projectionCoverage, up to 270 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectionCoverage Context triple: [ScreenX multi‑projection system, projectionCoverage, up to 270 degrees]
-
A.
regionCoverage
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
B.
mapCoverage
Indicates the extent or area that is represented, covered, or included by a particular map.
-
C.
scaleCoverage
Indicates adjusting the extent or scope of coverage, typically by increasing or decreasing it according to some scale or demand.
-
D.
stageCoverage
Indicates that one entity provides or has coverage, representation, or support for another within a particular stage or phase of a process or workflow.
-
E.
projectionRequirement
Indicates a requirement that one entity be projected, mapped, or represented onto another according to specified criteria or constraints.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb92ee27408190b0116ef2d789abac |
completed | May 6, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.