Triple
T1177136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John of Patmos |
E25052
|
entity |
| Predicate | selfDescribedAs |
P4296
|
FINISHED |
| Object | your brother and partner in tribulation |
—
|
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: your brother and partner in tribulation | Statement: [John of Patmos, selfDescribedAs, your brother and partner in tribulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selfDescribedAs Context triple: [John of Patmos, selfDescribedAs, your brother and partner in tribulation]
-
A.
isFrequentlyDescribedAs
Indicates that something is often characterized or referred to using a particular description or set of attributes.
-
B.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
C.
describedByAuthorAs
Indicates that one entity is characterized, labeled, or portrayed in a particular way by an author.
-
D.
selfIdentification
chosen
Indicates that an entity defines or declares its own identity, attributes, or classification about itself.
-
E.
hasDescription
Indicates that an entity is associated with a textual description that explains or characterizes it.
- 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_69a494267b4c819088c97a59182bf56a |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd53e4b48190abb2167f8074a6bc |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5844348190b01ac6506906ba3b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.