Triple
T28389163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiankeng Three Bridges |
E719102
|
entity |
| Predicate | literalMeaningOfChineseName |
P163761
|
FINISHED |
| Object | Three Bridges over Tiankengs |
—
|
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: Three Bridges over Tiankengs | Statement: [Tiankeng Three Bridges, literalMeaningOfChineseName, Three Bridges over Tiankengs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literalMeaningOfChineseName Context triple: [Tiankeng Three Bridges, literalMeaningOfChineseName, Three Bridges over Tiankengs]
-
A.
ChineseNameMeaning
chosen
Indicates that the predicate specifies the semantic meaning or interpretation of a given Chinese name.
-
B.
hasMeaningInChinese
Indicates that one entity (such as a word, phrase, or symbol) possesses a specific meaning or interpretation within the Chinese language.
-
C.
ChineseNameTraditional
Indicates that an entity’s name is given in traditional Chinese characters.
-
D.
birthNameMeaning
Indicates the semantic meaning or significance associated with a person's birth name.
-
E.
currentNameMeaning
Indicates that the predicate expresses the meaning or significance of an entity’s current name.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 1:12 a.m.