Triple
T24280177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | peci |
E605513
|
entity |
| Predicate | historicallyPopularizedBy |
P4586
|
FINISHED |
| Object | Sukarno |
—
|
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: Sukarno | Statement: [peci, historicallyPopularizedBy, Sukarno]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyPopularizedBy Context triple: [peci, historicallyPopularizedBy, Sukarno]
-
A.
popularizedBy
chosen
Indicates that something became widely known, accepted, or fashionable as a result of the influence or actions of a particular agent.
-
B.
popularizedIn
Indicates that something became widely known, accepted, or fashionable within a particular place, time period, or context.
-
C.
popularizedByWork
Indicates that something became widely known, accepted, or influential as a result of a particular work (such as a book, film, or artwork).
-
D.
popularizedAfter
Indicates that one entity became widely known, accepted, or influential only after another specified entity had already gained popularity.
-
E.
historicallyPopularIn
Indicates that something was notably popular or widely favored within a particular place or context during a past historical period.
- 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_69f28f51050481908a9bd3c586702057 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.