Triple
T3808495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abram |
E93069
|
entity |
| Predicate | originalFormOf |
P6483
|
FINISHED |
| Object | patriarch Abraham in the Bible |
—
|
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: patriarch Abraham in the Bible | Statement: [Abram, originalFormOf, patriarch Abraham in the Bible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalFormOf Context triple: [Abram, originalFormOf, patriarch Abraham in the Bible]
-
A.
originalForm
chosen
Indicates that one entity is the earlier, source, or initial version from which another entity is derived or transformed.
-
B.
originalType
Indicates that one entity represents the initial or source type from which another entity is derived, transformed, or reclassified.
-
C.
wasOriginally
Indicates that an entity had a particular state, form, type, or affiliation at an earlier time, which has since changed.
-
D.
formerType
Indicates that one entity previously had a certain type, role, or classification but no longer does.
-
E.
originalText
Indicates that one text is the initial, unmodified version from which other versions, translations, or representations are derived.
- 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_69aed96a60088190ab1df8390fffc935 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69aee7461abc8190945716f4b93e1a18 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:16 p.m.