Triple
T30498719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Succoth |
E776078
|
entity |
| Predicate | roleInGenesis |
P200001
|
FINISHED |
| Object | place where Jacob built booths for his livestock |
—
|
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: place where Jacob built booths for his livestock | Statement: [Succoth, roleInGenesis, place where Jacob built booths for his livestock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInGenesis Context triple: [Succoth, roleInGenesis, place where Jacob built booths for his livestock]
-
A.
roleInOrigin
Indicates that an entity holds or held a specific role, function, or position within the context of its origin or source.
-
B.
roleInCosmos
Indicates the function, position, or significance an entity holds within the larger structure or order of the cosmos.
-
C.
roleInExodus
Indicates that an entity has a specific role or function within the context of the Exodus event or narrative.
-
D.
roleInDUNE
Indicates that an entity has a specific acting role or participation in the production of the film "Dune."
-
E.
founderRole
Indicates that an entity serves as a founder in relation to another entity, specifying the role or capacity in which they established it.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff6a4ce9a08190b98abde3a170dd69 |
completed | May 9, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69ff69c11634819089d1084bd2c11534 |
completed | May 9, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69ff6a4c32dc819097f591944bee8851 |
completed | May 9, 2026, 5:09 p.m. |
Created at: April 29, 2026, 8:14 p.m.