Triple
T18807926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vicken Parsons |
E459927
|
entity |
| Predicate | typicalWorkScale |
P87672
|
FINISHED |
| Object | small-scale |
—
|
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: small-scale | Statement: [Vicken Parsons, typicalWorkScale, small-scale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWorkScale Context triple: [Vicken Parsons, typicalWorkScale, small-scale]
-
A.
workScale
chosen
Indicates the relative magnitude, intensity, or scope at which a given work activity, project, or operation is carried out.
-
B.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
C.
typicalWorkflow
Indicates that one process, sequence, or set of actions represents the standard or commonly followed way of performing a task or achieving a goal.
-
D.
standardizedWork
Indicates that an entity follows a defined, consistent method or procedure that has been formally established as the standard way of performing a task or process.
-
E.
workPeriod
Indicates the span of time during which an entity is engaged in a particular work or employment 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_69e5a3d8ab9c819097834eac798ce810 |
completed | April 20, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.