Triple
T14638371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Free Cities |
E343661
|
entity |
| Predicate | currencyUsage |
P188
|
FINISHED |
| Object | various local coins |
—
|
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: various local coins | Statement: [Free Cities, currencyUsage, various local coins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyUsage Context triple: [Free Cities, currencyUsage, various local coins]
-
A.
chargeOftenUsed
Indicates that an entity is frequently subjected to or associated with a particular charge (such as a legal, financial, or electrical charge).
-
B.
billingMetric
Indicates a relationship where a specific metric or measure is used as the basis for calculating billing or charges between entities.
-
C.
chargesBasedOn
Indicates that one party determines or applies a fee, price, or cost to another party or item according to a specified basis, criterion, or reference.
-
D.
usesCurrency
chosen
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
-
E.
gridUsage
Indicates how much and in what way an entity consumes or relies on a shared grid-based resource, such as an electrical or data grid.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4aca6448190adf1042dfbfef716 |
completed | April 14, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69de657359c88190b082e3e9f86fc1d7 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:26 a.m.