Triple
T24276679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hari Pahlawan |
E605428
|
entity |
| Predicate | hasSymbolicLocation |
P30881
|
FINISHED |
| Object | Surabaya |
—
|
NE NERFINISHED |
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: Surabaya | Statement: [Hari Pahlawan, hasSymbolicLocation, Surabaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSymbolicLocation Context triple: [Hari Pahlawan, hasSymbolicLocation, Surabaya]
-
A.
hasSymbolLocation
chosen
Indicates that a symbol is associated with or positioned at a specific location.
-
B.
locatedInSymbolicContext
Indicates that one entity is situated within or associated with another entity in an abstract, conceptual, or symbolic context rather than a strictly physical one.
-
C.
hasSymbolicValue
Indicates that something holds meaning, significance, or representational value beyond its literal or practical function.
-
D.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
E.
hasRelativeLocation
Indicates that one entity is positioned in space in relation to another entity’s location.
- F. None of above.
Provenance (3 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28d5fd03481908e502c6944d7fe69 |
completed | April 29, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.