Triple
T14418034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subiyah |
E357506
|
entity |
| Predicate | hasPlannedProjects |
P114178
|
FINISHED |
| Object | large-scale development 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: large-scale development projects | Statement: [Subiyah, hasPlannedProjects, large-scale development projects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedProjects Context triple: [Subiyah, hasPlannedProjects, large-scale development projects]
-
A.
hasProject
Indicates that an entity is associated with or responsible for a particular project.
-
B.
hasMaintenanceProjectsBy
Indicates that one entity is responsible for or associated with carrying out maintenance projects on another entity.
-
C.
hasProjectIn
Indicates that an entity is involved with or associated with a project that takes place within a specified location or context.
-
D.
hasNotableProject
Indicates that an entity is associated with a project that is distinguished or recognized as significant in some way.
-
E.
hasPlanningStatus
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
- F. None of above. chosen
Provenance (4 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90cec8e4819087c72d82f9caacda |
completed | April 14, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:17 a.m.