Triple
T24717791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piedras Blancas elephant seal rookery |
E612208
|
entity |
| Predicate | viewingDistanceRegulated |
P157026
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Piedras Blancas elephant seal rookery, viewingDistanceRegulated, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewingDistanceRegulated Context triple: [Piedras Blancas elephant seal rookery, viewingDistanceRegulated, yes]
-
A.
intendedViewingDistance
Indicates the distance at which something is meant or designed to be viewed or observed.
-
B.
viewingIs
Indicates that one entity is engaged in the act or state of viewing, observing, or watching another entity.
-
C.
viewingDistanceOnClearDay
Indicates the maximum distance from which one entity can be clearly seen or visually perceived by another under clear weather conditions.
-
D.
viewingMethod
Indicates the manner or technique by which something is observed, displayed, or visually accessed.
-
E.
hasViewingAngles
Indicates that one entity possesses or is characterized by specific viewing angles relative to another entity or reference frame.
- 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_69e2d7d6e7a48190bb43b0d8bb1137a0 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f410fc18808190b4e47d5a71d3a126 |
completed | May 1, 2026, 2:33 a.m. |
Created at: April 18, 2026, 3:39 a.m.