Triple
T19928516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Shepherd (angel of repentance) |
E478989
|
entity |
| Predicate | perceivedStatusInText |
P106752
|
FINISHED |
| Object | authoritative revealer |
—
|
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: authoritative revealer | Statement: [the Shepherd (angel of repentance), perceivedStatusInText, authoritative revealer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perceivedStatusInText Context triple: [the Shepherd (angel of repentance), perceivedStatusInText, authoritative revealer]
-
A.
statusInText
Indicates that the text explicitly states or conveys the status or condition of an entity.
-
B.
textStatus
Indicates the current state or condition of a piece of text, such as its progress, validity, or processing outcome.
-
C.
statusRelativeTo
Indicates the comparative state or condition of one entity in relation to another at a given point or over a period of time.
-
D.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
E.
hasStatusInText
chosen
Indicates that a particular status or state is explicitly mentioned or described within a given text.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659cd4500819090363a4b7d6bf193 |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.