Triple
T35118796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tysha |
E1014112
|
entity |
| Predicate | marriageCeremonyOfficiant |
P26980
|
FINISHED |
| Object | a drunken septon |
—
|
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: a drunken septon | Statement: [Tysha, marriageCeremonyOfficiant, a drunken septon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageCeremonyOfficiant Context triple: [Tysha, marriageCeremonyOfficiant, a drunken septon]
-
A.
ceremonyTypeOfficiated
Indicates the specific type of ceremony that an officiant conducted or presided over.
-
B.
marriageContractConductedBy
chosen
Indicates that a specific marriage contract or ceremony is formally carried out, officiated, or administered by a particular agent or authority.
-
C.
weddingRole
Indicates the specific role or function an entity has in the context of a wedding event.
-
D.
ceremonyPresidedBy
Indicates that a ceremony is overseen, led, or officially conducted by a particular person or authority.
-
E.
officiatedEvent
Indicates that an entity formally presided over, supervised, or conducted an event in an official capacity.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: May 3, 2026, 4:01 p.m.