Triple
T30407006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fantom |
E773506
|
entity |
| Predicate | hasTransactionFinalityTime |
P189698
|
FINISHED |
| Object | ~1 second |
—
|
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: ~1 second | Statement: [Fantom, hasTransactionFinalityTime, ~1 second]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransactionFinalityTime Context triple: [Fantom, hasTransactionFinalityTime, ~1 second]
-
A.
finalityType
Indicates the specific kind or category of finality or conclusiveness that applies to a given situation, decision, or state.
-
B.
typicalSettlementTime
chosen
Indicates the usual or expected amount of time it takes for a transaction or obligation to be fully settled.
-
C.
settlementPeriod
Indicates the length of time between a transaction or agreement and its final settlement or completion.
-
D.
hasTimeDepth
Indicates that something possesses or spans a measurable extent of time, such as duration, historical depth, or temporal layering.
-
E.
endTimeInGenesis
Indicates the time at which an event or state concludes within the temporal framework defined by the Genesis context or system.
- 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_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
Created at: April 29, 2026, 8:04 p.m.