Triple
T33683475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romanian leu |
E862962
|
entity |
| Predicate | subunitSingular |
P167180
|
FINISHED |
| Object | ban |
—
|
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: ban | Statement: [Romanian leu, subunitSingular, ban]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subunitSingular Context triple: [Romanian leu, subunitSingular, ban]
-
A.
subunitNameSingular
chosen
Indicates that the predicate specifies the singular form of the name for a subunit within a larger entity or structure.
-
B.
subunitOf
Indicates that one entity functions as a component or smaller part within the structure or organization of another, larger entity.
-
C.
subunitType
Indicates that one entity is a specific kind or classification of subunit within the structure or composition of another entity.
-
D.
typicalSubunitOf
Indicates that something is a standard or commonly occurring subcomponent or part of a larger whole.
-
E.
formerSubunit
Indicates that one entity was previously a subunit or subordinate part of another entity, but no longer holds that status.
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:43 a.m.