Triple
T29310477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanjung Tuan Forest Reserve |
E743217
|
entity |
| Predicate | raptorMigrationPeak |
P115351
|
FINISHED |
| Object | around March |
—
|
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: around March | Statement: [Tanjung Tuan Forest Reserve, raptorMigrationPeak, around March]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raptorMigrationPeak Context triple: [Tanjung Tuan Forest Reserve, raptorMigrationPeak, around March]
-
A.
timeOfMigration
chosen
Indicates the specific time or period during which a migration event occurs.
-
B.
populationAtPeak
Indicates that an entity’s population size is measured at its highest recorded level during a specified time or condition.
-
C.
deploymentPeakNumber
Indicates the maximum number of deployments (or deployment instances) reached during a specified period or under given conditions.
-
D.
directionOfMigration
Indicates the geographic direction or path along which a migration movement proceeds from its origin toward its destination.
-
E.
yearOfMajorMigration
Indicates the specific year in which a significant migration event involving the subject took place.
- 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f665e3d30481909b5b20cf5dc252d1 |
completed | May 2, 2026, 9 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:16 p.m.