Triple
T19039638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gastraea theory |
E465967
|
entity |
| Predicate | proposesAncestor |
P133657
|
FINISHED |
| Object | gastraea |
—
|
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: gastraea | Statement: [Gastraea theory, proposesAncestor, gastraea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposesAncestor Context triple: [Gastraea theory, proposesAncestor, gastraea]
-
A.
hasAncestor
Indicates that one entity is an ancestor (direct or indirect, such as a parent, grandparent, etc.) of another entity in a genealogical or hierarchical lineage.
-
B.
producedAncestorOf
Indicates that one entity is an ancestor of another in a production or derivation chain, having directly or indirectly produced it through intermediate steps.
-
C.
typeOfAncestor
Indicates that one entity is an ancestor (of any generational distance) of another entity.
-
D.
progenitorOf
Indicates that one entity is the direct biological or ancestral source (parent or originator) of another entity.
-
E.
possibleDescendant
Indicates that one entity may be a descendant of another, without asserting that the descendant relationship is certain.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d7ff9b6c8190adc3917a8c9af7bd |
completed | April 20, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69e4a3001e388190aa6057266514e75a |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8f6f7c8190af645bf08823ee2b |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 12:02 p.m.