Triple
T24248465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hagrites |
E603446
|
entity |
| Predicate | sourceTextDetail |
P131980
|
FINISHED |
| Object | 1 Chronicles 5:10 |
—
|
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: 1 Chronicles 5:10 | Statement: [Hagrites, sourceTextDetail, 1 Chronicles 5:10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceTextDetail Context triple: [Hagrites, sourceTextDetail, 1 Chronicles 5:10]
-
A.
typicalSourceText
Indicates that the related entity is a common or representative textual source from which information, examples, or data about another entity are typically drawn.
-
B.
source
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
C.
textContent
Indicates that one entity is the textual content or written material contained within another entity.
-
D.
textSources
chosen
Indicates that one entity serves as a source or origin for the text content associated with another entity.
-
E.
documentSource
Indicates that one entity serves as the origin, provider, or provenance source for a given document.
- 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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28b87d03c8190a38ca0c0b65ce6fc |
completed | April 29, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:04 a.m.