Triple
T37518589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | painter's algorithm |
E932700
|
entity |
| Predicate | typicalPrimitives |
P107341
|
FINISHED |
| Object | polygons |
—
|
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: polygons | Statement: [painter's algorithm, typicalPrimitives, polygons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPrimitives Context triple: [painter's algorithm, typicalPrimitives, polygons]
-
A.
usesPrimitiveType
Indicates that one entity employs or relies on a specified primitive data type in its definition or implementation.
-
B.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
-
C.
hasPrimitive
chosen
Indicates that an entity is composed of, defined by, or associated with one or more basic, indivisible components or elements.
-
D.
typicalCoreType
Indicates that something is a standard or characteristic core type within a given classification or system.
-
E.
typicalSymbol
Indicates that something serves as a characteristic or commonly recognized symbol representing something else.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.