Triple
T37897285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mulgore |
E945313
|
entity |
| Predicate | resourceNodes |
P166170
|
FINISHED |
| Object | herbs |
—
|
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: herbs | Statement: [Mulgore, resourceNodes, herbs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resourceNodes Context triple: [Mulgore, resourceNodes, herbs]
-
A.
resourceSystem
Indicates a relationship where one entity functions as or belongs to a system that manages, allocates, or organizes resources for another entity or context.
-
B.
resourceExtracted
Indicates that a resource has been obtained or taken from a source entity, typically through an extraction process.
-
C.
targetResource
Indicates that one entity designates another entity as the specific resource or object toward which an action, request, or operation is directed.
-
D.
includesResources
Indicates that one entity contains, encompasses, or makes available specific resources as part of its composition or offering.
-
E.
hostsResource
chosen
Indicates that one entity provides the environment or infrastructure in which another entity (the resource) resides, is stored, or is made available.
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:19 p.m.