Triple
T30406854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ren Project |
E773503
|
entity |
| Predicate | requiresStakeAmount |
P31816
|
FINISHED |
| Object | 100000 REN |
—
|
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: 100000 REN | Statement: [Ren Project, requiresStakeAmount, 100000 REN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresStakeAmount Context triple: [Ren Project, requiresStakeAmount, 100000 REN]
-
A.
requiresBalanceWith
Indicates that one entity’s state, quantity, or action must be countered or matched by another to maintain an overall balance or equilibrium.
-
B.
hasStake
Indicates that one entity holds an interest, share, or involvement—financial, strategic, or otherwise—in another entity or outcome.
-
C.
requiresMinimumCapital
chosen
Indicates that one entity can only proceed, be valid, or be permitted if a specified minimum amount of capital is available or provided.
-
D.
collateralRequired
Indicates that a party must provide collateral as a condition or security for an obligation, transaction, or agreement.
-
E.
feeRequirement
Indicates that a payment or fee must be provided or satisfied as a condition for a particular action, service, or relationship to occur or remain valid.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: April 29, 2026, 8:04 p.m.