Triple
T18138631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argentine National Parks System |
E434200
|
entity |
| Predicate | activityRegulated |
P51774
|
FINISHED |
| Object | tourism |
—
|
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: tourism | Statement: [Argentine National Parks System, activityRegulated, tourism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activityRegulated Context triple: [Argentine National Parks System, activityRegulated, tourism]
-
A.
activityControlled
Indicates that one entity regulates, directs, or manages the activity or behavior of another entity.
-
B.
activityTime
Indicates the time period during which an activity occurs or is scheduled to take place.
-
C.
activitiesRestricted
Indicates that certain actions or behaviors are limited, prohibited, or constrained under specified conditions or for particular entities.
-
D.
activityType
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
-
E.
hasActivityRegulation
chosen
Indicates that one entity exerts control over the level, timing, or manner of another entity’s activity.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de0993e88190b19c5cb35a6d252d |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.