Triple
T32996814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PN Hoffman |
E844252
|
entity |
| Predicate | hasDevelopmentStageCoverage |
P47059
|
FINISHED |
| Object | land acquisition to stabilization |
—
|
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: land acquisition to stabilization | Statement: [PN Hoffman, hasDevelopmentStageCoverage, land acquisition to stabilization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDevelopmentStageCoverage Context triple: [PN Hoffman, hasDevelopmentStageCoverage, land acquisition to stabilization]
-
A.
hasDevelopmentStatus
Indicates the current stage or condition of progress or completion that something is in.
-
B.
hasDevelopmentType
Indicates the type or category of development associated with an entity, such as the nature, form, or stage of its development.
-
C.
hasCoverage
Indicates that one entity provides insurance or protection coverage for another entity or subject.
-
D.
hasDevelopmentDynamic
Indicates that one entity exhibits a pattern, rate, or mode of change or growth over time in relation to another entity or context.
-
E.
hasDevelopmentDimension
chosen
Indicates that something possesses or is associated with a particular aspect or dimension of development.
- 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: May 1, 2026, 1:22 a.m.