Triple
T28837987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoàn Kiếm (Returned Sword) legend |
E728236
|
entity |
| Predicate | explainsNameOf |
P7885
|
FINISHED |
| Object | Hoàn Kiếm Lake |
—
|
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: Hoàn Kiếm Lake | Statement: [Hoàn Kiếm (Returned Sword) legend, explainsNameOf, Hoàn Kiếm Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explainsNameOf Context triple: [Hoàn Kiếm (Returned Sword) legend, explainsNameOf, Hoàn Kiếm Lake]
-
A.
nameOf
Indicates that one entity is the name or designation of another entity.
-
B.
reasonForName
chosen
Indicates the explanation or cause behind why an entity has a particular name.
-
C.
namedAccordingTo
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
-
D.
knowsAs
Indicates that one entity recognizes or refers to another entity by a particular name, alias, or identifier.
-
E.
nameLiterallyMeans
Indicates that the literal meaning or direct translation of one entity’s name is given by the other entity.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6596fae5c81908eb8abb59acf3471 |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:39 a.m.