Triple
T22797594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PC Zone |
E564291
|
entity |
| Predicate | platformCoverage |
P149749
|
FINISHED |
| Object | PC |
—
|
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: PC | Statement: [PC Zone, platformCoverage, PC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformCoverage Context triple: [PC Zone, platformCoverage, PC]
-
A.
screenCoverage
Indicates the extent to which one entity visually occupies or covers the display area of another (e.g., how much of a screen is taken up by a given element).
-
B.
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.
-
C.
dataCoverage
Indicates the extent or proportion of relevant data that is included, captured, or represented within a given dataset or system.
-
D.
networkCoverage
Indicates the extent to which a network’s signal or service is available across a given area or to specific entities.
-
E.
platformIncludes
Indicates that a platform contains, supports, or provides access to the specified component, feature, or content.
- 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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17cda76448190891c5190e1d75ae0 |
completed | April 29, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:30 p.m.