Triple
T31139987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exodos |
E793753
|
entity |
| Predicate | hasTypicalParticipants |
P154005
|
FINISHED |
| Object | actors |
—
|
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: actors | Statement: [Exodos, hasTypicalParticipants, actors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalParticipants Context triple: [Exodos, hasTypicalParticipants, actors]
-
A.
hasParticipants
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
B.
hasTypicalAttendance
Indicates the usual or characteristic number of attendees associated with an event, venue, or activity.
-
C.
typicalParticipation
chosen
Indicates that an entity commonly or characteristically takes part in a particular activity, event, or process.
-
D.
traditionalParticipantsType
Indicates the type or category of participants involved in a traditional or customary context or activity.
-
E.
hasLimitedParticipation
Indicates that an entity is involved in an activity, event, or process only to a restricted or constrained extent, rather than with full participation.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: April 29, 2026, 9:05 p.m.