Triple
T8401073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urban Renewal Administration |
E198170
|
entity |
| Predicate | typeOfProjectFinanced |
P37446
|
FINISHED |
| Object | slum clearance 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: slum clearance projects | Statement: [Urban Renewal Administration, typeOfProjectFinanced, slum clearance projects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfProjectFinanced Context triple: [Urban Renewal Administration, typeOfProjectFinanced, slum clearance projects]
-
A.
typeOfProject
Indicates the specific category or kind of project that an entity is associated with or classified under.
-
B.
eligibleProjectType
Indicates that a project belongs to a category or type that qualifies it for a specific program, process, or benefit.
-
C.
notableProjectType
Indicates the type or category of a project for which an entity is particularly well-known or notable.
-
D.
typicalProjectTypes
chosen
Indicates the kinds or categories of projects that are most commonly or characteristically associated with a given entity.
-
E.
funderType
Indicates the category or kind of organization or individual that provides funding in the relationship.
- 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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb824da3148190bfa3a1abfdfa02de |
completed | March 31, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:04 p.m.