Triple
T25891322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of David |
E652340
|
entity |
| Predicate | traditionalEndPoint |
P15546
|
FINISHED |
| Object | Babylonian conquest of Judah |
—
|
NE NERFINISHED |
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: Babylonian conquest of Judah | Statement: [House of David, traditionalEndPoint, Babylonian conquest of Judah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalEndPoint Context triple: [House of David, traditionalEndPoint, Babylonian conquest of Judah]
-
A.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
B.
typicalEndpoint
Indicates that something represents the standard or commonly used endpoint associated with another entity or process.
-
C.
traditionalEnd
chosen
Indicates that one entity is the customary or historically established conclusion, outcome, or final stage of another entity or process.
-
D.
endPointExample
Indicates that something serves as a representative or illustrative instance of a particular endpoint.
-
E.
secondaryEndpoint
Indicates that something serves as an additional, non-primary endpoint or target associated with a main endpoint in a relationship or process.
- 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_69e7ab3c6cc081908de59bfcc28ec19d |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 22, 2026, 8:21 a.m.