Triple
T6535489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BIFF Square |
E152347
|
entity |
| Predicate | hasSignageIn |
P71497
|
FINISHED |
| Object | Korean |
—
|
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: Korean | Statement: [BIFF Square, hasSignageIn, Korean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignageIn Context triple: [BIFF Square, hasSignageIn, Korean]
-
A.
hasSignage
Indicates that appropriate signs or visual markers are present to convey information, directions, warnings, or identification related to the associated entity.
-
B.
hasSignageType
Indicates the specific category or kind of signage associated with an object, location, or entity.
-
C.
hasSignageName
Indicates that an entity has a specific name or label as it appears on its physical signage.
-
D.
hasSignagePrefix
Indicates that one signage element begins with or contains another signage element as its initial segment or prefix.
-
E.
signageStandard
Indicates that something conforms to, follows, or specifies a particular standard or convention for signage.
- 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_69c688048ec8819093a47f7d332e12ec |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6adc05da88190b402085954cec8e0 |
completed | March 27, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69c68abd9c7c819099e4fe8097cd1b28 |
completed | March 27, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69c69f362ee4819090e8fa48caef7d7d |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 1:46 p.m.