Triple
T24024999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manaen |
E594927
|
entity |
| Predicate | sourceTextStatus |
P134245
|
FINISHED |
| Object | only explicitly mentioned once in the New Testament |
—
|
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: only explicitly mentioned once in the New Testament | Statement: [Manaen, sourceTextStatus, only explicitly mentioned once in the New Testament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceTextStatus Context triple: [Manaen, sourceTextStatus, only explicitly mentioned once in the New Testament]
-
A.
sourceStatus
Indicates the current state or condition of a given source within a process, system, or workflow.
-
B.
originalTextStatus
Indicates the relationship between a text and its current state or condition relative to its original, unmodified form.
-
C.
sourceState
Indicates the original or starting state from which a transition, change, or process begins.
-
D.
textStatus
Indicates the current state or condition of a piece of text, such as its progress, validity, or processing outcome.
-
E.
statusInText
chosen
Indicates that the text explicitly states or conveys the status or condition of an entity.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d769f7248190ae145218fb0e8bbd |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:53 p.m.