Triple
T7643000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bashful |
E173052
|
entity |
| Predicate | notablePhysicalCharacteristic |
P31173
|
FINISHED |
| Object | often blushing |
—
|
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: often blushing | Statement: [Bashful, notablePhysicalCharacteristic, often blushing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePhysicalCharacteristic Context triple: [Bashful, notablePhysicalCharacteristic, often blushing]
-
A.
hasPhysicalFeature
chosen
Indicates that one entity possesses or exhibits a specific physical characteristic or feature of another entity.
-
B.
notableFeatureOn
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
-
C.
physicalCharacteristics
Indicates that one entity has or describes the bodily or material attributes, features, or appearance of another entity.
-
D.
biologicalCharacteristic
Indicates that one entity possesses or exhibits a particular biological trait, feature, or property in relation to another.
-
E.
legCharacteristic
Indicates a characteristic, property, or attribute that specifically pertains to the legs of an 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_69c6995360188190968ee57b72a1627f |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6faef96908190a7724b204f9d8c9e |
completed | March 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e8cadc8190b7977fcd213954dd |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:58 p.m.