Triple
T20223429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosalind and Orlando |
E495315
|
entity |
| Predicate | endOfPlayEvent |
P17625
|
FINISHED |
| Object | marriage ceremony in the Forest of Arden |
—
|
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: marriage ceremony in the Forest of Arden | Statement: [Rosalind and Orlando, endOfPlayEvent, marriage ceremony in the Forest of Arden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfPlayEvent Context triple: [Rosalind and Orlando, endOfPlayEvent, marriage ceremony in the Forest of Arden]
-
A.
endEvent
Indicates that one event or process marks the termination or conclusion of another event or process.
-
B.
isFinalPlayBy
Indicates that a particular play or move is the last one performed by a specified entity in a sequence or event.
-
C.
endOfActivity
chosen
Indicates that a particular activity has reached its completion or final point in time.
-
D.
eventResult
Indicates that one event occurs as a consequence or outcome of another event.
-
E.
sportsEventFinish
Indicates the outcome or completion status of a sports event, typically linking the event to its final result or placement of participants.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd827708190b798a30f4e7d533f |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.