Triple
T360252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iacomus |
E7834
|
entity |
| Predicate | ultimatelyFrom |
P1257
|
FINISHED |
| Object | Biblical Hebrew Yaʿaqov |
—
|
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: Biblical Hebrew Yaʿaqov | Statement: [Iacomus, ultimatelyFrom, Biblical Hebrew Yaʿaqov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ultimatelyFrom Context triple: [Iacomus, ultimatelyFrom, Biblical Hebrew Yaʿaqov]
-
A.
derivedFrom
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
B.
upstreamFrom
Indicates that one entity is located or occurs earlier in the flow or sequence relative to another, typically in a direction opposite to the main movement or progression.
-
C.
transmittedFrom
Indicates that something (such as information, a signal, or a disease) has been passed or conveyed from one source entity to another.
-
D.
emergedFrom
chosen
Indicates that one entity originated, arose, or came forth from another entity or source.
-
E.
formedBy
Indicates that something comes into existence or is created as a result of a specific agent, process, or combination of components.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebccb8d88190a31f7c443a0c8566 |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95aeed48190b5e48865cc964938 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.