Triple
T11199802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hannibal (temporarily influenced region) |
E265008
|
entity |
| Predicate | temporaryStatus |
P50685
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hannibal (temporarily influenced region), temporaryStatus, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporaryStatus Context triple: [Hannibal (temporarily influenced region), temporaryStatus, yes]
-
A.
temporaryOutcome
Indicates that a result or state produced by an action or process is provisional and expected to change or be replaced later.
-
B.
temporaryAnthemStatus
Indicates that an anthem is designated to serve in a provisional or interim capacity rather than as the permanent official anthem.
-
C.
isTemporary
chosen
Indicates that the relationship, state, or condition holds only for a limited or non-permanent duration.
-
D.
temporaryControl
Indicates that one entity has non-permanent, time-limited authority or influence over another entity or resource.
-
E.
status
Indicates the current condition, state, or standing of an entity within a given context.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8c1e9f88190b2b42326aba9d778 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:29 p.m.