Triple
T37961097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wandering Trader |
E947009
|
entity |
| Predicate | tradeLimit |
P189670
|
FINISHED |
| Object | each trade has limited uses |
—
|
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: each trade has limited uses | Statement: [Wandering Trader, tradeLimit, each trade has limited uses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradeLimit Context triple: [Wandering Trader, tradeLimit, each trade has limited uses]
-
A.
monetaryLimit
Indicates a constraint or maximum allowable amount of money associated with an action, transaction, or relationship.
-
B.
tier2InvestorLimit
Indicates that there is a maximum allowable amount or capacity specifically applicable to Tier 2 investors within a given context or system.
-
C.
investorLimitTier1
Indicates the maximum allowable participation or allocation for investors classified in the first (highest-priority) limit tier.
-
D.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
E.
distributionLimitWest
Indicates a constraint or boundary on how far westward something may be distributed or extended.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc7b6c2c88190ad4f58980834053c |
completed | May 6, 2026, 10:59 p.m. |
Created at: May 3, 2026, 4:20 p.m.