Triple
T11317000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five-hundred-meter Aperture Spherical Telescope |
E267992
|
entity |
| Predicate | openForOperationsDate |
P30383
|
FINISHED |
| Object | 2020-01 |
—
|
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: 2020-01 | Statement: [Five-hundred-meter Aperture Spherical Telescope, openForOperationsDate, 2020-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openForOperationsDate Context triple: [Five-hundred-meter Aperture Spherical Telescope, openForOperationsDate, 2020-01]
-
A.
openedAt
chosen
Indicates that an entity began operating, became accessible, or was first made available at a specific time or date.
-
B.
softOpeningDate
Indicates the date on which a business, venue, or service begins limited or trial operations before its official grand opening.
-
C.
fullOperationDate
Indicates the date on which an operation or process is fully carried out or becomes completely effective.
-
D.
operatorStartDate
Indicates the date on which an operator’s role, activity, or responsibility begins.
-
E.
retailTrancheOpeningDate
Indicates the date on which a retail tranche (the portion of an offering allocated to retail investors) is first opened or made available.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9c3cf748190987838029d9f7fff |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.