Triple
T35599369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naresuan Bridge (Phitsanulok) |
E1028724
|
entity |
| Predicate | namedForHistoricalFigure |
P185676
|
FINISHED |
| Object | Naresuan the Great |
—
|
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: Naresuan the Great | Statement: [Naresuan Bridge (Phitsanulok), namedForHistoricalFigure, Naresuan the Great]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForHistoricalFigure Context triple: [Naresuan Bridge (Phitsanulok), namedForHistoricalFigure, Naresuan the Great]
-
A.
namedForCulturalFigure
Indicates that one entity is named in honor of, or derived from the name of, a notable cultural figure.
-
B.
historicalFigure
Indicates that an entity is recognized as a notable person from the past who played a significant role in history.
-
C.
namedForPoliticalFigure
chosen
Indicates that one entity is named in honor of, or after, a specific political figure.
-
D.
addressesHistoricalFigure
Indicates that one entity directly speaks or writes to a person recognized as a historical figure.
-
E.
basedOnHistoricalFigure
Indicates that something is derived from, inspired by, or modeled after a real historical person.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 3, 2026, 4:05 p.m.