Triple
T31083856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UPC-E |
E792173
|
entity |
| Predicate | quietZoneSide |
P170729
|
FINISHED |
| Object | left |
—
|
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: left | Statement: [UPC-E, quietZoneSide, left]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: quietZoneSide Context triple: [UPC-E, quietZoneSide, left]
-
A.
sideDenyingIntrusion
Indicates that one side is actively preventing or rejecting an attempted intrusion by another.
-
B.
noisePolicy
Indicates the rules or constraints governing acceptable noise levels or noise-related behavior in a given context.
-
C.
zonedTo
Indicates that one entity is assigned or designated to fall within the jurisdiction, service area, or regulatory zone of another entity.
-
D.
zonedUse
Indicates the designated or permitted type of land use assigned to a property or area under zoning regulations.
-
E.
zoneBased
Indicates that the relationship or action is determined or constrained by specific geographic or logical zones.
- 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695fb5f60819099ac1f20472cfc61 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 29, 2026, 9:02 p.m.