Triple
T24695478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagi tree |
E611571
|
entity |
| Predicate | believedToProvide |
P156998
|
FINISHED |
| Object | protection |
—
|
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: protection | Statement: [Nagi tree, believedToProvide, protection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: believedToProvide Context triple: [Nagi tree, believedToProvide, protection]
-
A.
aimsToProvide
Indicates that one entity intends or is designed to supply, deliver, or make available something to another entity.
-
B.
sometimesProvides
Indicates that one entity occasionally or intermittently provides something (such as a service, resource, or support) to another entity, but not on a consistent or guaranteed basis.
-
C.
providesThat
Indicates that one entity stipulates, specifies, or sets forth a condition, rule, or provision that applies to another entity or situation.
-
D.
providerOf
Indicates that one entity supplies, furnishes, or makes available a good, service, or resource to another entity.
-
E.
providesServices
Indicates that one entity supplies or performs services for the benefit or use of another entity.
- 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_69e2c4d76d148190b58ad612467149a5 |
completed | April 17, 2026, 11:40 p.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:21 a.m.