Triple
T4923635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whyte notation |
E110523
|
entity |
| Predicate | classifiesBy |
P25488
|
FINISHED |
| Object | wheel arrangement |
—
|
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: wheel arrangement | Statement: [Whyte notation, classifiesBy, wheel arrangement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classifiesBy Context triple: [Whyte notation, classifiesBy, wheel arrangement]
-
A.
areClassifiedBy
chosen
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.
definesClassification
Indicates that one entity specifies or establishes the classification or category to which another entity belongs.
-
D.
classificationBySP
Indicates a relationship where an entity is categorized or classified according to a specific standard, scheme, or specification (SP).
-
E.
usesClassifiers
Indicates that one entity employs or relies on a system of classifiers (such as category labels or measure words) when referring to or organizing another entity.
- 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffd46748190843fed99f02fd8d5 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3695c8819094e7ad2f6d4ba1ac |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.