Triple
T15849963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merarites |
E384307
|
entity |
| Predicate | allocatedCitiesIn |
P120755
|
FINISHED |
| Object | territory of Reuben |
—
|
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: territory of Reuben | Statement: [Merarites, allocatedCitiesIn, territory of Reuben]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allocatedCitiesIn Context triple: [Merarites, allocatedCitiesIn, territory of Reuben]
-
A.
gatheredCities
Indicates that one entity collected or assembled multiple cities together, typically into a group, list, or shared context.
-
B.
numberOfAutonomousCities
Indicates the count of autonomous cities associated with a given entity.
-
C.
isPlannedCity
Indicates that a city has been deliberately designed and constructed according to a pre-established urban plan rather than developing organically over time.
-
D.
hasPlannedCity
Indicates that an entity has a city that was deliberately designed and constructed according to a prearranged plan.
-
E.
hasNumberOfComponentCities
Indicates the relationship that specifies how many component cities are contained within or associated with a given entity.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142b976c081908d3ba3e705419f3a |
completed | April 16, 2026, 8:12 p.m. |
| PDg | Predicate description generation | batch_69e174da2c2c819099ec46616798245a |
completed | April 16, 2026, 11:46 p.m. |
Created at: April 10, 2026, 4:50 a.m.