Triple
T25114227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | povo |
E629081
|
entity |
| Predicate | planCharacteristic |
P32324
|
FINISHED |
| Object | customizable plans |
—
|
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: customizable plans | Statement: [povo, planCharacteristic, customizable plans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planCharacteristic Context triple: [povo, planCharacteristic, customizable plans]
-
A.
policyCharacteristic
Indicates that a policy possesses a particular attribute, feature, or quality that characterizes how it is defined or operates.
-
B.
projectCharacteristics
Indicates the defining features, qualities, or attributes that characterize a particular project.
-
C.
managementCharacteristic
Indicates a defining quality, style, or attribute associated with how something is managed or administered.
-
D.
entityCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular characteristic or attribute.
-
E.
hasPlanningCharacteristic
chosen
Indicates that an entity possesses a specific feature, quality, or attribute related to planning activities or processes.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f46579b7708190bc899259bf755f58 |
completed | May 1, 2026, 8:34 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:27 a.m.