Triple
T12732563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tychicus |
E304277
|
entity |
| Predicate | possiblyServedAs |
P106622
|
FINISHED |
| Object | interim leader in Ephesus |
—
|
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: interim leader in Ephesus | Statement: [Tychicus, possiblyServedAs, interim leader in Ephesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possiblyServedAs Context triple: [Tychicus, possiblyServedAs, interim leader in Ephesus]
-
A.
alsoServesAs
Indicates that one entity has an additional role, function, or identity that it fulfills simultaneously with its primary one.
-
B.
typicallyServedAs
Indicates that something is most commonly presented, used, or offered in a particular role, form, or function.
-
C.
alsoServedBy
Indicates that the same service, function, or role is additionally provided or fulfilled by another entity alongside the primary one.
-
D.
alsoServedAs
Indicates that an entity held an additional role or position beyond the primary one already mentioned.
-
E.
isServedFor
Indicates that something is provided or presented as suitable or intended for a particular purpose, use, or recipient.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:25 p.m.