Triple
T216788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss franc |
E4121
|
entity |
| Predicate | pegStatus |
P2876
|
FINISHED |
| Object | free-floating |
—
|
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: free-floating | Statement: [Swiss franc, pegStatus, free-floating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pegStatus Context triple: [Swiss franc, pegStatus, free-floating]
-
A.
peakStatus
Indicates the condition or phase of something at its highest or most intense point in its progression or lifecycle.
-
B.
isPegged
chosen
Indicates that one entity’s value, status, or behavior is fixed or tightly linked to that of another entity, typically so that changes in the reference entity directly determine changes in the pegged entity.
-
C.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
D.
deFactoStatus
Indicates that one entity holds a role, position, or status in practice or by custom, even if it is not formally or legally recognized.
-
E.
canonicalStatus
Indicates the formal or official standing of an entity within an established authoritative or normative 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c4edfa081909fe97c86c3c7801d |
completed | Feb. 28, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69a25b5357bc8190b29a48e3053fb76d |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.