Triple
T23636662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pachoras |
E583765
|
entity |
| Predicate | earlierCulturalPhase |
P120347
|
FINISHED |
| Object | Nubian |
—
|
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: Nubian | Statement: [Pachoras, earlierCulturalPhase, Nubian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierCulturalPhase Context triple: [Pachoras, earlierCulturalPhase, Nubian]
-
A.
culturalPeriod
Indicates the historical or cultural era with which an entity is associated or during which it was created, used, or significant.
-
B.
culturalPhase
chosen
Indicates the specific cultural or stylistic period to which an entity (such as an artifact, site, or work) is assigned within a broader historical or archaeological sequence.
-
C.
earlierFortificationCulture
Indicates that one culture’s fortification activity or tradition chronologically precedes that of another culture.
-
D.
earlierPhaseReligion
Indicates that one religious phase, tradition, or development chronologically precedes another in a given historical or doctrinal sequence.
-
E.
earlierDynasty
Indicates that one dynasty chronologically precedes another in historical succession.
- 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_69e248fe1c2c8190ac914d2442ff3d26 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b1ed03148190a14b3c81ebf7ed99 |
completed | April 29, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:47 p.m.