Triple
T28534485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulhi Falhu |
E722124
|
entity |
| Predicate | hasDevelopmentProjectType |
P12865
|
FINISHED |
| Object | land reclamation project |
—
|
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: land reclamation project | Statement: [Gulhi Falhu, hasDevelopmentProjectType, land reclamation project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDevelopmentProjectType Context triple: [Gulhi Falhu, hasDevelopmentProjectType, land reclamation project]
-
A.
hasDevelopmentType
Indicates the type or category of development associated with an entity, such as the nature, form, or stage of its development.
-
B.
hasDevelopmentStatus
Indicates the current stage or condition of progress or completion that something is in.
-
C.
hasProjectType
chosen
Indicates that an entity is associated with, or classified under, a specific type or category of project.
-
D.
hasDeveloperType
Indicates that an entity is associated with a specific category or type of developer.
-
E.
hasComponentDevelopment
Indicates that an entity is involved in or responsible for the development of one or more of its components.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: April 28, 2026, 3:31 a.m.