Triple
T33049804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiketidai |
E845691
|
entity |
| Predicate | hasSurvivingTextStatus |
P87573
|
FINISHED |
| Object | substantially extant |
—
|
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: substantially extant | Statement: [Hiketidai, hasSurvivingTextStatus, substantially extant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurvivingTextStatus Context triple: [Hiketidai, hasSurvivingTextStatus, substantially extant]
-
A.
hasSurvivingText
chosen
Indicates that there exists at least one extant or preserved textual record associated with the subject.
-
B.
hasSurvivalStatus
Indicates the survival condition or outcome associated with an entity, such as whether it is alive, deceased, or in another defined survival state.
-
C.
hasStatusInText
Indicates that a particular status or state is explicitly mentioned or described within a given text.
-
D.
hasSurvivingElement
Indicates that an entity retains at least one remaining or extant part, instance, or component that still exists.
-
E.
hasSurvivalElements
Indicates that something includes features or conditions related to survival, such as resource management, threat avoidance, or sustaining life over time.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
Created at: May 1, 2026, 1:24 a.m.