Triple
T8663431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ta Hien Street |
E205602
|
entity |
| Predicate | hasEstablishment |
P83958
|
FINISHED |
| Object | bars |
—
|
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: bars | Statement: [Ta Hien Street, hasEstablishment, bars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEstablishment Context triple: [Ta Hien Street, hasEstablishment, bars]
-
A.
establishedAs
Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
-
B.
officeEstablishedWith
Indicates that an office or formal workplace was created or set up through the involvement, authorization, or collaboration of the associated entity or entities.
-
C.
establishedOffice
Indicates that an entity created or set up an official office or place of operation.
-
D.
legalEstablishment
Indicates that an entity has been formally created, recognized, or brought into existence according to legal rules or procedures.
-
E.
hasThermalEstablishment
Indicates that one entity is responsible for creating, setting, or defining the thermal conditions or temperature state of another entity.
- 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_69ca83516ae88190aefe034b3bc589e3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc489f7edc8190bde1b4dc09249207 |
completed | March 31, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:30 p.m.