Triple
T9122399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reed Dance |
E218885
|
entity |
| Predicate | involvesParticipantRole |
P15562
|
FINISHED |
| Object | maidens presenting reeds |
—
|
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: maidens presenting reeds | Statement: [Reed Dance, involvesParticipantRole, maidens presenting reeds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesParticipantRole Context triple: [Reed Dance, involvesParticipantRole, maidens presenting reeds]
-
A.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
B.
involvedActor
chosen
Indicates that an entity participates as an actor or participant in the referenced event, activity, or situation.
-
C.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
D.
determinesParticipantIn
Indicates that one entity has the authority or role to decide or specify which other entity (or entities) will participate in a given event, activity, or process.
-
E.
intraPartyRole
Indicates a role or function that an entity holds within a specific political party or internal party structure.
- 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8b46dac8190bde88205c85f596a |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:17 p.m.