Triple
T29604154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pom de dalt |
E754530
|
entity |
| Predicate | typicalParticipantBuild |
P203773
|
FINISHED |
| Object | lightest participants |
—
|
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: lightest participants | Statement: [pom de dalt, typicalParticipantBuild, lightest participants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalParticipantBuild Context triple: [pom de dalt, typicalParticipantBuild, lightest participants]
-
A.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
B.
typicalParticipation
Indicates that an entity commonly or characteristically takes part in a particular activity, event, or process.
-
C.
traditionalParticipantsType
Indicates the type or category of participants involved in a traditional or customary context or activity.
-
D.
typicalProfile
Indicates that an entity represents the standard or most representative profile or pattern for another entity.
-
E.
participantFrom
Indicates that a participant originates from, is associated with, or comes out of a specified source, group, or context.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a01f4d954e08190aff3756955212d67 |
completed | May 11, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_6a01edadb9248190be592287530740a5 |
completed | May 11, 2026, 2:54 p.m. |
| PDg | Predicate description generation | batch_6a01f4d84fa08190be6dea78f3fa9d8c |
completed | May 11, 2026, 3:25 p.m. |
Created at: April 28, 2026, 6:24 p.m.