Triple
T21815072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Picardan |
E538584
|
entity |
| Predicate | bodyContribution |
P145766
|
FINISHED |
| Object | light body |
—
|
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: light body | Statement: [Picardan, bodyContribution, light body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyContribution Context triple: [Picardan, bodyContribution, light body]
-
A.
contributionBased
Indicates that something is determined, allocated, or structured according to the level or amount of contributions made by the involved entities.
-
B.
contributionBase
Indicates the foundational amount, value, or resource on which a contribution, payment, or benefit is calculated or determined.
-
C.
primaryContributionOf
Indicates that one entity is the main or most significant contribution made by another entity.
-
D.
portraysContribution
Indicates that one entity depicts, represents, or illustrates the contribution or role of another entity.
-
E.
contributionToWork
Indicates a relationship where an entity has provided effort, input, or resources that help create, develop, or complete a particular work.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07cc99bbc8190bf074930f361af7d |
completed | April 28, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6c670ee608190b9cfdc09de74f0de |
completed | April 21, 2026, 12:36 a.m. |
Created at: April 16, 2026, 6:54 p.m.