Triple
T24381926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gadites |
E614633
|
entity |
| Predicate | inheritanceConfirmedBy |
P653
|
FINISHED |
| Object | Joshua |
—
|
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: Joshua | Statement: [Gadites, inheritanceConfirmedBy, Joshua]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inheritanceConfirmedBy Context triple: [Gadites, inheritanceConfirmedBy, Joshua]
-
A.
inheritanceStatus
Indicates the type or condition of inheritance rights or succession status that applies between related parties.
-
B.
confirmedBy
chosen
Indicates that one entity validates, approves, or verifies the truth, accuracy, or occurrence of another entity or event.
-
C.
attestedBy
Indicates that the existence, occurrence, or validity of something is supported, confirmed, or documented by a specified source or authority.
-
D.
discoveryConfirmedBy
Indicates that a discovery has been validated or corroborated by a particular source, authority, or piece of evidence.
-
E.
agreedHeir
Indicates that one entity has been formally designated and accepted as the heir of another, typically through mutual agreement or legal arrangement.
- 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293dc0c3c8190ad6de5db50ccbd76 |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:03 a.m.