Triple
T23668872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arun Valley SSSI |
E584667
|
entity |
| Predicate | hasInterestType |
P152915
|
FINISHED |
| Object | biological |
—
|
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: biological | Statement: [Arun Valley SSSI, hasInterestType, biological]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInterestType Context triple: [Arun Valley SSSI, hasInterestType, biological]
-
A.
hasPolicyInterestOf
Indicates that one entity holds or is associated with a specific policy interest belonging to or concerning another entity.
-
B.
subjectInterest
Indicates that the subject has an interest in, or is concerned with, the object.
-
C.
hasOverlappingInterestsFrom
Indicates that one entity shares some, but not necessarily all, interests in common with another entity, such that their sets of interests partially overlap.
-
D.
hasVisitorInterest
Indicates that an entity has a particular interest, preference, or attraction toward visiting another entity or location.
-
E.
interestMayBe
Indicates that one entity potentially has an interest in, or may be interested in, another entity or subject.
- 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_69e24901421881908c17a5293bdd4a8e |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b40d0e208190969fecbede5979b8 |
completed | April 29, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:50 p.m.