Triple
T15050938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English Market |
E379357
|
entity |
| Predicate | hasLowerLevelUse |
P116541
|
FINISHED |
| Object | fresh food stalls |
—
|
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: fresh food stalls | Statement: [English Market, hasLowerLevelUse, fresh food stalls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLowerLevelUse Context triple: [English Market, hasLowerLevelUse, fresh food stalls]
-
A.
lowerLevelUsedFor
Indicates that a lower-level component, resource, or abstraction is utilized to implement, support, or realize the functionality of a higher-level one.
-
B.
hasUsageLevel
Indicates the degree or intensity with which something is used or utilized.
-
C.
hasUpperLevelFunction
Indicates that one function operates at a higher or more abstract level than another function within a hierarchical relationship.
-
D.
hasLowerTier
Indicates that one entity is ranked, valued, or classified at a lower level or tier relative to another entity.
-
E.
hasLowerLevelLine
Indicates that one line is positioned or ranked below another line within a hierarchical or layered structure.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69deda8f71988190b4fe7f7de4ccb798 |
completed | April 15, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69de9a69d7848190b2b4662dd30f20e9 |
completed | April 14, 2026, 7:50 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 3:01 a.m.