Triple
T20416484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love's Labour's Won |
E500725
|
entity |
| Predicate | isPresumed |
P50642
|
FINISHED |
| Object | lost |
—
|
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: lost | Statement: [Love's Labour's Won, isPresumed, lost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPresumed Context triple: [Love's Labour's Won, isPresumed, lost]
-
A.
presumption
Indicates that one party assumes or takes for granted a particular fact, condition, or state about another, often without definitive proof.
-
B.
isAssumedIn
chosen
Indicates that something is taken for granted or presumed to hold within a particular context, without requiring explicit proof or verification.
-
C.
isPer
Indicates that the subject entity is classified as a person.
-
D.
possibleJudgment
Indicates a potential or anticipated judgment, decision, or evaluative outcome that could be made about an entity or situation.
-
E.
assumes
Indicates that one entity takes on, accepts, or presumes a role, responsibility, state, or fact regarding another entity or situation.
- 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67a4437448190b07b6e6e3de5830f |
completed | April 20, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:30 a.m.