Triple
T23025147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persian traders |
E573286
|
entity |
| Predicate | usedKnowledge |
P33840
|
FINISHED |
| Object | monsoon wind patterns |
—
|
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: monsoon wind patterns | Statement: [Persian traders, usedKnowledge, monsoon wind patterns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedKnowledge Context triple: [Persian traders, usedKnowledge, monsoon wind patterns]
-
A.
usesKnowledgeOf
chosen
Indicates that one entity applies or draws upon the knowledge possessed by another entity in performing an action or achieving a result.
-
B.
knows
Indicates that one entity has knowledge or awareness of another entity or piece of information.
-
C.
knowledgeType
Indicates the specific category or nature of knowledge associated with an entity or statement (e.g., factual, procedural, conceptual).
-
D.
knownToBe
Indicates that one entity is recognized or acknowledged as being a certain way, having a certain property, or fitting a particular description by others.
-
E.
knowledgeExchange
Indicates a reciprocal sharing or transfer of knowledge, information, or expertise between entities.
- 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_69e245b821008190b0e09cb02092aae1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1847c671c8190a8095051d8c3cf93 |
completed | April 29, 2026, 4:09 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:52 p.m.