Triple
T38588866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Festergut |
E932406
|
entity |
| Predicate | relatedEncounter |
P206556
|
FINISHED |
| Object | Rotface encounter |
—
|
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: Rotface encounter | Statement: [Festergut, relatedEncounter, Rotface encounter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedEncounter Context triple: [Festergut, relatedEncounter, Rotface encounter]
-
A.
followsEncounter
Indicates that one encounter occurs after and in sequence with another encounter.
-
B.
encounterID
Indicates a unique identifier that links all data and events associated with a single encounter or interaction between entities.
-
C.
relatedCohort
Indicates that two or more entities are associated through membership in, or connection to, the same cohort or grouped population.
-
D.
encounterOrder
Indicates the sequence in which entities meet or come into contact with each other.
-
E.
relatedCase
Indicates that one legal case is connected or associated with another case, such as through shared facts, parties, issues, or procedural history.
- F. None of above. chosen
Provenance (4 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c85e308819083dd67b96f457659 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:32 p.m.