Triple
T38539952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qiongzhou Strait fixed link |
E924803
|
entity |
| Predicate | discussionPeriod |
P190881
|
FINISHED |
| Object | since late 20th century |
—
|
LITERAL FINISHED |
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: since late 20th century | Statement: [Qiongzhou Strait fixed link, discussionPeriod, since late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discussionPeriod Context triple: [Qiongzhou Strait fixed link, discussionPeriod, since late 20th century]
-
A.
discussionPublic
Indicates that a discussion is accessible to the general public rather than being restricted or private.
-
B.
discussionStyle
Indicates the manner or approach with which one party conducts or participates in a discussion with another.
-
C.
discussed
Indicates that one entity talked about, examined, or debated a topic, issue, or other entity with someone else.
-
D.
discussionsTo
Indicates a relationship in which one entity leads to, results in, or gives rise to discussions involving another entity.
-
E.
discourse
Indicates that one entity engages in extended verbal or written communication or discussion with another entity.
- F. None of above. chosen
Provenance (4 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd34596288190b8e34a7a20b4c0db |
completed | May 7, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f81cbc8190b4fd3bfc3106c1f3 |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd2e2f00081908b8c820fc073a63c |
completed | May 7, 2026, 5:58 p.m. |
Created at: May 3, 2026, 4:32 p.m.