Triple
T17018542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biological Dynamics of Forest Fragments Project |
E412883
|
entity |
| Predicate | hasResearchSiteType |
P21545
|
FINISHED |
| Object | forest fragments |
—
|
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: forest fragments | Statement: [Biological Dynamics of Forest Fragments Project, hasResearchSiteType, forest fragments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResearchSiteType Context triple: [Biological Dynamics of Forest Fragments Project, hasResearchSiteType, forest fragments]
-
A.
hasCapitalSiteType
Indicates the type or classification of the site that serves as the capital for an entity.
-
B.
containsResearchStation
Indicates that one entity geographically includes or hosts a research station within its boundaries.
-
C.
researchSite
chosen
Indicates that a location serves as a site where research or investigative studies are conducted or based.
-
D.
hasArchaeologicalSiteType
Indicates that an entity is classified as, or associated with, a specific type or category of archaeological site.
-
E.
hasStudyAreaType
Indicates that an entity’s study area is classified as a specific type or category (e.g., lab, field site, classroom).
- 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d481a0988190a13d0928e0c7ebbf |
completed | April 18, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.