Triple
T5339532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thing 2 |
E123910
|
entity |
| Predicate | partnerInMischief |
P21638
|
FINISHED |
| Object | Thing 1 |
—
|
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: Thing 1 | Statement: [Thing 2, partnerInMischief, Thing 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerInMischief Context triple: [Thing 2, partnerInMischief, Thing 1]
-
A.
partnerInMyth
Indicates a mythological relationship in which two entities are partners or companions within the same myth or mythic narrative.
-
B.
partnerInCrime
chosen
Indicates a relationship where two or more entities collaborate closely in committing or planning wrongful, illicit, or mischievous acts together.
-
C.
partnerInMission
Indicates that two or more entities collaborate as partners in carrying out the same mission or operation.
-
D.
partnerInStory
Indicates that two or more entities are partners or collaborators within the context of a specific story or narrative.
-
E.
coProtagonist
Indicates that two or more entities share the primary leading role together in the same narrative work.
- 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85e86edc81908d87933db6489f91 |
completed | March 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69bd845a62b081909782863865b257a9 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.