Triple
T30500761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scarf |
E776129
|
entity |
| Predicate | hasTypicalPattern |
P8151
|
FINISHED |
| Object | solid color |
—
|
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: solid color | Statement: [Scarf, hasTypicalPattern, solid color]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalPattern Context triple: [Scarf, hasTypicalPattern, solid color]
-
A.
hasTypicalSequence
Indicates that there is a usual or commonly occurring order or progression in which the related entities or events take place.
-
B.
hasPattern
chosen
Indicates that one entity exhibits, follows, or is characterized by a specific recurring form, structure, or design defined by another entity.
-
C.
hasTraditionalPatternsType
Indicates that one entity is associated with a specific type or category of traditional patterns present in or applied to it.
-
D.
hasUsePattern
Indicates a characteristic or recurring way in which something is typically used or applied.
-
E.
hasTypicalUsageType
Indicates that something is associated with a standard or commonly expected way in which it is used.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: April 29, 2026, 8:14 p.m.