Triple
T6673551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribe of Naphtali |
E151792
|
entity |
| Predicate | allotmentRecordedIn |
P28051
|
FINISHED |
| Object | Joshua 19 |
—
|
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: Joshua 19 | Statement: [Tribe of Naphtali, allotmentRecordedIn, Joshua 19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allotmentRecordedIn Context triple: [Tribe of Naphtali, allotmentRecordedIn, Joshua 19]
-
A.
hasLandAllotmentDescribedIn
chosen
Indicates that an entity’s land allotment is specified or detailed in a particular document or description.
-
B.
landTenure
Indicates the type, conditions, or rights under which land is held, used, or owned by an entity.
-
C.
isRecordedInDomesdayBook
Indicates that an entity is documented as existing or being held in the historical Domesday Book survey.
-
D.
landGrantField
Indicates that a specific field or parcel of land has been allocated or granted, typically by an authority, to a recipient under a land grant arrangement.
-
E.
landholderIn
Indicates that one entity holds legal or recognized ownership or tenancy rights over land located within the jurisdiction or bounds of another entity.
- 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_69c687f830bc81909eb8b04dbb8450b1 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:03 p.m.