Triple
T18803330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Works Division |
E459810
|
entity |
| Predicate | projectLifecycleRole |
P124720
|
FINISHED |
| Object | planning of works 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: planning of works projects | Statement: [Works Division, projectLifecycleRole, planning of works projects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectLifecycleRole Context triple: [Works Division, projectLifecycleRole, planning of works projects]
-
A.
roleInProjectLifecycle
chosen
Indicates the specific function or responsibility an entity has at a particular stage of a project's lifecycle.
-
B.
roleInCompanyLifecycle
Indicates the specific function or responsibility an entity has at a particular stage of a company's lifecycle.
-
C.
portfolioRole
Indicates the specific function, capacity, or position an entity holds within a portfolio or collection of assets.
-
D.
plannedRole
Indicates that an entity is expected or intended to assume a particular role or function in a planned or future context.
-
E.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
- 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.