Triple
T25043057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asterix |
E627162
|
entity |
| Predicate | inspiredThemePark |
P157918
|
FINISHED |
| Object | Parc Astérix |
—
|
NE NERFINISHED |
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: Parc Astérix | Statement: [Asterix, inspiredThemePark, Parc Astérix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredThemePark Context triple: [Asterix, inspiredThemePark, Parc Astérix]
-
A.
inspiredThemeParkElement
Indicates that one element of a theme park is conceptually based on, influenced by, or derived from another source or idea.
-
B.
themeParkAttractionAt
Indicates that a specific theme park attraction is located at or associated with a particular theme park or site.
-
C.
themeParkAttraction
Indicates that something is an attraction or ride located within a theme park.
-
D.
themeParkConnection
Indicates a relationship where two or more entities are connected through a theme park, such as by location, operation, partnership, or shared attractions.
-
E.
hasThemePark
Indicates that one entity owns, contains, or is associated with a theme park as part of its properties or offerings.
- 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_69e2ff2b4c80819087c916b2b16241b9 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4530d80148190b959bb48ff7e0c2f |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 18, 2026, 6:08 a.m.