Triple
T18803327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Works Division |
E459810
|
entity |
| Predicate | projectTypeHandled |
P4243
|
FINISHED |
| Object | public buildings |
—
|
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 buildings | Statement: [Works Division, projectTypeHandled, public buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectTypeHandled Context triple: [Works Division, projectTypeHandled, public buildings]
-
A.
hasProjectType
Indicates that an entity is associated with, or classified under, a specific type or category of project.
-
B.
supportsProjectType
chosen
Indicates that one entity is capable of handling, accommodating, or being compatible with a specified type of project.
-
C.
eligibleProjectType
Indicates that a project belongs to a category or type that qualifies it for a specific program, process, or benefit.
-
D.
typicalProjectTypes
Indicates the kinds or categories of projects that are most commonly or characteristically associated with a given entity.
-
E.
typeOfProject
Indicates the specific category or kind of project that an entity is associated with or classified under.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a0253f748190998995e3b1524357 |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.