Triple
T28380098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ULURP |
E718867
|
entity |
| Predicate | startTrigger |
P194741
|
FINISHED |
| Object | application certification as complete |
—
|
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: application certification as complete | Statement: [ULURP, startTrigger, application certification as complete]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTrigger Context triple: [ULURP, startTrigger, application certification as complete]
-
A.
startDuring
Indicates that one event or interval begins at some point strictly within the duration of another event or interval, but not at its start.
-
B.
startingGuard
Indicates that an entity serves as the primary or first-choice guard in a lineup, formation, or configuration.
-
C.
exportStart
Indicates the point in time or event at which an export process or outbound transfer of goods, data, or resources begins.
-
D.
startedNear
Indicates that one event or action began close in time or space to another event or action.
-
E.
startMethod
Indicates that one entity initiates or begins the execution of a method associated with another entity.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
| PDg | Predicate description generation | batch_69fd8640e1d4819081c98f15eeb221ab |
completed | May 8, 2026, 6:44 a.m. |
Created at: April 28, 2026, 1:06 a.m.