Triple
T38251501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 56 Up |
E1014060
|
entity |
| Predicate | hasParticipantGroupSize |
P95118
|
FINISHED |
| Object | 14 original participants (some absent in later films) |
—
|
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: 14 original participants (some absent in later films) | Statement: [56 Up, hasParticipantGroupSize, 14 original participants (some absent in later films)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParticipantGroupSize Context triple: [56 Up, hasParticipantGroupSize, 14 original participants (some absent in later films)]
-
A.
hasMaximumNumberOfMembers
Indicates that there is an upper limit on how many members can be associated with a given entity.
-
B.
hasAudienceSize
Indicates the relationship between an entity and the number of people or size of group that receives, views, or engages with it.
-
C.
sizeOfGroup
chosen
Indicates the number of individuals or elements that make up a particular group.
-
D.
hasAttendeeGroup
Indicates that an event or activity is associated with a specific group of attendees considered collectively.
-
E.
hasParticipants
Indicates that an event, activity, or situation involves one or more entities as participants in it.
- 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_69f76dd7e89c8190b7866bc85aea521b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a007899cadc8190a04edd503eaf6514 |
completed | May 10, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_6a0078493e088190b0c5047cbe75d304 |
completed | May 10, 2026, 12:21 p.m. |
Created at: May 3, 2026, 4:30 p.m.