Triple
T19906295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Wood |
E478425
|
entity |
| Predicate | mayBeClassifiedBy |
P14654
|
FINISHED |
| Object | grain pattern |
—
|
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: grain pattern | Statement: [De Wood, mayBeClassifiedBy, grain pattern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeClassifiedBy Context triple: [De Wood, mayBeClassifiedBy, grain pattern]
-
A.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
B.
isClassifiedUnder
Indicates that one entity is categorized or grouped within a broader class, type, or category represented by another entity.
-
C.
isSometimesClassifiedAs
chosen
Indicates that an entity is occasionally, but not consistently or universally, categorized under a particular type or class.
-
D.
usesClassificationCriteria
Indicates that one entity applies specific classification criteria to categorize, organize, or evaluate another entity.
-
E.
supportsClassificationUpTo
Indicates that one entity provides assistance, resources, or functionality enabling another entity to perform classification tasks up to a specified level, scope, or complexity.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65946916881909c3f52208c07aa64 |
completed | April 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.