Triple
T8968086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herbert Tichy |
E214188
|
entity |
| Predicate | continentOfMajorActivity |
P8233
|
FINISHED |
| Object | Asia |
—
|
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: Asia | Statement: [Herbert Tichy, continentOfMajorActivity, Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continentOfMajorActivity Context triple: [Herbert Tichy, continentOfMajorActivity, Asia]
-
A.
continentOfActivity
chosen
Indicates the continent on which an entity primarily operates, is active, or conducts its main activities.
-
B.
continentType
Indicates that one entity is classified as a specific type or category of continent in relation to another entity.
-
C.
continentInvolved
Indicates that a particular continent participates in, is affected by, or plays a role in a specified event, process, or relationship.
-
D.
continentB
Indicates that the subject entity is a continent that contains or is associated with the object entity (such as a country, region, or location).
-
E.
continentSystem
Indicates a relationship where a continent is part of, or associated with, a particular planetary or geographic system.
- 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_69ca839dbf608190a2f5990477115d29 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6764aca48190a5e472d1b6841886 |
completed | April 1, 2026, 12:31 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed9a2d48190ad11381078e823b7 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:01 p.m.