Triple
T8150697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-shares |
E190324
|
entity |
| Predicate | typicalTradingBoardLot |
P3664
|
FINISHED |
| Object | 100 shares |
—
|
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: 100 shares | Statement: [A-shares, typicalTradingBoardLot, 100 shares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTradingBoardLot Context triple: [A-shares, typicalTradingBoardLot, 100 shares]
-
A.
typicalGoodsSold
Indicates the kinds of goods or products that an entity most commonly or characteristically sells.
-
B.
typicalUnitConfiguration
Indicates the standard or commonly used arrangement, composition, or setup of a unit in a given context.
-
C.
typicalDimension
Indicates that one entity represents a standard or characteristic measurement (such as size, length, or capacity) typically associated with another entity.
-
D.
typicalUnitSize
chosen
Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
-
E.
typicalUnitType
Indicates that one entity is the standard or commonly used unit type associated with measuring or expressing the other entity.
- 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_69ca82be7ba8819087de0147e9292c83 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4481f19c8190aeec9bf029ad321b |
completed | March 31, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:37 p.m.