Triple
T32148929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slim |
E821099
|
entity |
| Predicate | typicalBearersCharacteristic |
P140235
|
FINISHED |
| Object | slender build |
—
|
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: slender build | Statement: [Slim, typicalBearersCharacteristic, slender build]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBearersCharacteristic Context triple: [Slim, typicalBearersCharacteristic, slender build]
-
A.
typicalBearers
Indicates that certain entities are the usual or characteristic holders, users, or possessors of a given property, role, or attribute.
-
B.
typicalNameBearers
Indicates that the subject is a common or characteristic name borne by the entities in the object set.
-
C.
typicalBearersNationality
Indicates the nationality that entities of a given type or class are most commonly associated with.
-
D.
bearerStyleCharacteristic
chosen
Indicates that a bearer (such as a person or object) exhibits or is associated with a particular style-related characteristic.
-
E.
hasMultipleBearers
Indicates that a single item, attribute, or role is associated with more than one bearer or holder simultaneously.
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:31 a.m.