Triple
T29289182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Housing Development Corporation |
E742610
|
entity |
| Predicate | isDeveloperFor |
P139242
|
FINISHED |
| Object | Hulhumalé land reclamation projects |
—
|
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: Hulhumalé land reclamation projects | Statement: [Housing Development Corporation, isDeveloperFor, Hulhumalé land reclamation projects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDeveloperFor Context triple: [Housing Development Corporation, isDeveloperFor, Hulhumalé land reclamation projects]
-
A.
hasDeveloperType
Indicates that an entity is associated with a specific category or type of developer.
-
B.
isDevelopedBy
Indicates that something (such as a product, project, or idea) is created, produced, or brought into existence through the work or effort of a particular developer or group of developers.
-
C.
hasDeveloperRelation
chosen
Indicates a relationship in which one entity serves as the developer, creator, or builder of another entity.
-
D.
supportsDeveloper
Indicates that one entity provides assistance, resources, or advocacy to help a developer perform their work or achieve their goals.
-
E.
coDeveloperOf
Indicates that two or more entities jointly developed or collaborated in creating the same project, product, or work.
- 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_69f0912323c48190b9a24ef8cf359225 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6653e73e081908ea14f73f88d5648 |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:01 p.m.