Triple
T14650531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackberrying |
E343968
|
entity |
| Predicate | lineation |
P15027
|
FINISHED |
| Object | short lines |
—
|
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: short lines | Statement: [Blackberrying, lineation, short lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineation Context triple: [Blackberrying, lineation, short lines]
-
A.
lining
Indicates that one entity forms a layer or covering along the inner or outer surface of another entity.
-
B.
divisionLine
Indicates a boundary or separating line that divides one area, group, or portion from another.
-
C.
lineStandard
Indicates that one entity is a standard or reference specification that defines or governs the characteristics or requirements of a particular line (such as a product line, production line, or service line).
-
D.
lineType
chosen
Indicates the specific category or style of a line used in a representation, such as its function or visual convention.
-
E.
formedLine
Indicates that an entity has arranged itself or others into a line or linear formation.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4ed037c8190a87bf43f839fec05 |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:26 a.m.