Triple
T1983862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torrey Pines State Natural Reserve |
E43092
|
entity |
| Predicate | hasCommonTree |
P6706
|
FINISHED |
| Object | Torrey pine |
—
|
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: Torrey pine | Statement: [Torrey Pines State Natural Reserve, hasCommonTree, Torrey pine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonTree Context triple: [Torrey Pines State Natural Reserve, hasCommonTree, Torrey pine]
-
A.
hasTree
chosen
Indicates that one entity possesses, contains, or is associated with a tree.
-
B.
hasCommonAncestryGroup
Indicates that the related entities share membership in the same ancestral or lineage-based group.
-
C.
hasCommonValue
Indicates that two or more entities share at least one identical value or attribute in common.
-
D.
sharesCommonAncestorWith
Indicates that two entities have at least one ancestor in common in their lineage or hierarchy.
-
E.
hasNearbyCommon
Indicates that two entities share at least one common element, feature, or connection that is located within a specified nearby distance or vicinity.
- 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_69a88713ddc88190a969715658ebe7a8 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb96f932881908bebfc4176fda7c0 |
completed | March 7, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69abb798d288819083132cf14605bd02 |
completed | March 7, 2026, 5:28 a.m. |
Created at: March 4, 2026, 7:37 p.m.