Triple
T24971955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henoko |
E624913
|
entity |
| Predicate | hasDemonstrationsSince |
P162557
|
FINISHED |
| Object | late 1990s |
—
|
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: late 1990s | Statement: [Henoko, hasDemonstrationsSince, late 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDemonstrationsSince Context triple: [Henoko, hasDemonstrationsSince, late 1990s]
-
A.
hasDemonstration
Indicates that one entity includes, is accompanied by, or is associated with a demonstration or illustrative example of another entity or concept.
-
B.
demonstratedOn
Indicates that an action, behavior, or property is shown, illustrated, or proven using a particular entity as the example or subject.
-
C.
hasTypeOfDemonstration
Indicates that an event or action is characterized by a specific kind or category of demonstration.
-
D.
demonstratedAt
Indicates that an action, behavior, or capability was shown or exhibited at a particular event, location, or point in time.
-
E.
hasTechnologyDemonstration
Indicates that an entity includes, features, or is associated with a demonstration of a particular technology or technological capability.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f62b9e5ba88190a3c0d46edec7afe7 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f627ad6d4c81909796d39d78e414f9 |
completed | May 2, 2026, 4:34 p.m. |
Created at: April 18, 2026, 6:01 a.m.