Triple
T32054864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lepilemuridae |
E818588
|
entity |
| Predicate | restingSite |
P7849
|
FINISHED |
| Object | tree holes |
—
|
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: tree holes | Statement: [Lepilemuridae, restingSite, tree holes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restingSite Context triple: [Lepilemuridae, restingSite, tree holes]
-
A.
isSiteOf
chosen
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
B.
isKeySiteOf
Indicates that a location serves as an important or central place for a particular event, activity, process, or function.
-
C.
isTypeSiteOf
Indicates that a site serves as the specific location or setting where a particular type, category, or classification is realized or occurs.
-
D.
nearSiteOf
Indicates that one entity is located in close physical proximity to the site or location associated with another entity.
-
E.
developmentSiteOf
Indicates that a particular site or location is the place where a specified development project or construction activity occurs or is planned to occur.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4ee918c8190958db5d467458a6a |
completed | May 3, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:21 a.m.