Triple
T640153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolina pound |
E16719
|
entity |
| Predicate | subunitOfRatio |
P507
|
FINISHED |
| Object | 1 pound = 20 shillings |
—
|
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 pound = 20 shillings | Statement: [North Carolina pound, subunitOfRatio, 1 pound = 20 shillings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subunitOfRatio Context triple: [North Carolina pound, subunitOfRatio, 1 pound = 20 shillings]
-
A.
subunitRatio
chosen
Indicates the proportional relationship between the quantities or sizes of different subunits within a larger whole.
-
B.
subunitType
Indicates that one entity is a specific kind or classification of subunit within the structure or composition of another entity.
-
C.
formerSubunit
Indicates that one entity was previously a subunit or subordinate part of another entity, but no longer holds that status.
-
D.
subsidiaryUnit
Indicates that one organizational unit functions as a subordinate or dependent division of another, higher-level unit.
-
E.
dividedBy
Indicates that one quantity is separated into a specified number of equal parts or groups by another quantity, representing a division relationship between them.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49f0189b08190a584b744f36fa761 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0830008190a26ee158ed4dd1fe |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.