Triple
T25597093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Nectanebo |
E641683
|
entity |
| Predicate | hasDynast |
P159148
|
FINISHED |
| Object | Nectanebo I |
—
|
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: Nectanebo I | Statement: [House of Nectanebo, hasDynast, Nectanebo I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDynast Context triple: [House of Nectanebo, hasDynast, Nectanebo I]
-
A.
isDynastic
Indicates that a relationship, status, or succession is based on or belongs to a hereditary ruling family or lineage.
-
B.
hasDynasticFunction
Indicates that something serves a role or purpose within a dynasty, such as supporting its continuity, authority, or internal organization.
-
C.
hasLastDynasty
Indicates that an entity’s most recent or final ruling dynasty is the specified dynasty.
-
D.
hasDynasticConnections
Indicates that one entity is related to another through familial or hereditary ties between ruling or noble dynasties.
-
E.
hasDynasticLaw
Indicates that a political entity is governed by a specific set of hereditary succession rules or dynastic inheritance laws.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9a30ad081909c4acab2736475a1 |
completed | May 2, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 4:28 p.m.