Triple
T24695479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagi tree |
E611571
|
entity |
| Predicate | believedToProvide |
P156998
|
FINISHED |
| Object | good fortune |
—
|
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: good fortune | Statement: [Nagi tree, believedToProvide, good fortune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: believedToProvide Context triple: [Nagi tree, believedToProvide, good fortune]
-
A.
believedToProvide
chosen
Indicates that something is thought or assumed to offer or supply a particular benefit, effect, or resource.
-
B.
aimsToProvide
Indicates that one entity intends or is designed to supply, deliver, or make available something to another entity.
-
C.
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.
-
D.
providesThat
Indicates that one entity stipulates, specifies, or sets forth a condition, rule, or provision that applies to another entity or situation.
-
E.
providerOf
Indicates that one entity supplies, furnishes, or makes available a good, service, or resource to another entity.
- 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_69e2c4d76d148190b58ad612467149a5 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 3:21 a.m.