Triple
T25815049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colorino |
E650224
|
entity |
| Predicate | typicalBodyContribution |
P195222
|
FINISHED |
| Object | medium to full |
—
|
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: medium to full | Statement: [Colorino, typicalBodyContribution, medium to full]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBodyContribution Context triple: [Colorino, typicalBodyContribution, medium to full]
-
A.
bodyContribution
Indicates that an entity contributes a physical body or bodily component to another entity, process, or structure.
-
B.
mentionsBody
Indicates that one entity explicitly refers to or talks about the body of another entity (such as a person, organism, or physical form).
-
C.
typicalBodyType
Indicates that one entity is the usual or characteristic body type associated with another entity.
-
D.
publicBody
Indicates that an entity functions as a governmental or publicly controlled organization that performs public duties or services.
-
E.
supportingBody
Indicates that one entity serves as a supporting or backing body for another entity, providing endorsement, resources, or structural support.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
| PDg | Predicate description generation | batch_69fdb3172b808190b590d7c5be31ebb7 |
completed | May 8, 2026, 9:55 a.m. |
Created at: April 22, 2026, 7:25 a.m.