Triple
T18563781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shavian block |
E453709
|
entity |
| Predicate | isSupplementaryBlock |
P132507
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Shavian block, isSupplementaryBlock, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSupplementaryBlock Context triple: [Shavian block, isSupplementaryBlock, true]
-
A.
isSupplementaryPlane
Indicates that one plane serves as a supplementary or auxiliary plane to another, typically providing additional or supporting geometric or spatial information.
-
B.
isMajorBlockOf
Indicates that one entity constitutes a primary or principal portion, segment, or component of another entity.
-
C.
hasBlock
Indicates that one entity possesses, contains, or is associated with a specific block or blocking element in relation to another entity.
-
D.
hasSupplement
Indicates that one entity provides or is associated with an additional supporting or enhancing item, resource, or component for another entity.
-
E.
belongsToBlock
Indicates that something is a member or component of a specific block or grouping.
- F. None of above. chosen
Provenance (4 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53afc57448190abd90167d7e12a18 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:42 a.m.