Triple
T36401704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Five animals |
E896647
|
entity |
| Predicate | currentlyLinkedTo |
P200420
|
FINISHED |
| Object | photographic safaris |
—
|
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: photographic safaris | Statement: [Big Five animals, currentlyLinkedTo, photographic safaris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentlyLinkedTo Context triple: [Big Five animals, currentlyLinkedTo, photographic safaris]
-
A.
hasBeenLinkedTo
Indicates that an entity has been associated or connected with another entity, often suggesting a reported or inferred relationship between them.
-
B.
canBeLinkedTo
Indicates that one entity has the potential or capability to be connected or associated with another entity.
-
C.
associatedCurrent
Indicates a relationship where a particular current is linked or connected to another entity as its relevant or corresponding current.
-
D.
formerlyConnectedTo
Indicates that two entities were once connected or associated in some way, but that connection no longer exists.
-
E.
styleLinkedTo
Indicates a relationship where one style is associated with, derived from, or otherwise connected to another style.
- 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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff891e4b9c8190aa86a339a8944496 |
completed | May 9, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69ff8801180c8190b23e20996ca68e0a |
completed | May 9, 2026, 7:16 p.m. |
| PDg | Predicate description generation | batch_69ff891d54248190be8742197564605a |
completed | May 9, 2026, 7:21 p.m. |
Created at: May 3, 2026, 4:10 p.m.