Triple
T19784528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahanaim |
E475224
|
entity |
| Predicate | laterServedAs |
P90369
|
FINISHED |
| Object | administrative center in Gilead |
—
|
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: administrative center in Gilead | Statement: [Mahanaim, laterServedAs, administrative center in Gilead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterServedAs Context triple: [Mahanaim, laterServedAs, administrative center in Gilead]
-
A.
alsoServedAs
Indicates that an entity held an additional role or position beyond the primary one already mentioned.
-
B.
servedAs
Indicates that one entity held and performed the role, position, or function associated with another entity for some period of time.
-
C.
laterServedBy
chosen
Indicates that one entity is subsequently served or provided service by another entity at a later time.
-
D.
possiblyServedAs
Indicates that an entity may have held or fulfilled a particular role, position, or function, but this service is uncertain or not definitively confirmed.
-
E.
laterRepresented
Indicates that one entity subsequently served as an official representative or agent for another entity at a later time.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6538715b8819080c6930e7d16ab58 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.