Triple
T3376553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyderabad Metro |
E71079
|
entity |
| Predicate | projectModel |
P48074
|
FINISHED |
| Object | public–private partnership |
—
|
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: public–private partnership | Statement: [Hyderabad Metro, projectModel, public–private partnership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectModel Context triple: [Hyderabad Metro, projectModel, public–private partnership]
-
A.
project
Indicates that an entity plans, organizes, or carries out a structured effort or initiative aimed at achieving a specific goal or outcome.
-
B.
projectFaced
Indicates that a project encountered or experienced specific challenges, obstacles, or conditions during its course.
-
C.
parentProject
Indicates that one project serves as the direct higher-level or containing project in relation to another project.
-
D.
projectPromoter
Indicates that an entity is responsible for initiating, supporting, or advocating for a particular project.
-
E.
projectOutcome
Indicates the resulting state, impact, or consequences produced by carrying out a project.
- 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2e776508190bc123fb17b36f062 |
completed | March 8, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69ada433059881908e46f38cc5f40a32 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69adaa518ac88190b64f949ace018ab7 |
completed | March 8, 2026, 4:56 p.m. |
Created at: March 8, 2026, 3:13 p.m.