Triple
T27919281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astroland |
E706158
|
entity |
| Predicate | operatedCycloneUntil |
P6603
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Astroland, operatedCycloneUntil, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedCycloneUntil Context triple: [Astroland, operatedCycloneUntil, 2008]
-
A.
operatedCycloneFrom
Indicates that an agent operated or controlled a cyclone (such as a cyclone-related device, system, or operation) from a particular location or source.
-
B.
operatedUntil
chosen
Indicates that an entity continued to function or be in operation up to a specified end time or date.
-
C.
initiallyOperated
Indicates that an entity first began functioning, being used, or carrying out its intended operation at a specified initial time or under initial conditions.
-
D.
operatedBefore
Indicates that one entity performed an operation or action at an earlier time than another entity.
-
E.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: April 27, 2026, 6:55 p.m.