Triple
T30964151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 0857.HK |
E788903
|
entity |
| Predicate | hasListingBoardLot |
P193721
|
FINISHED |
| Object | 1000 |
—
|
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: 1000 | Statement: [0857.HK, hasListingBoardLot, 1000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasListingBoardLot Context triple: [0857.HK, hasListingBoardLot, 1000]
-
A.
hasListingBoard
Indicates that an entity is associated with or features a listing board used to display available items, offers, or information.
-
B.
hasListingNumber
Indicates that an entity is associated with a specific listing identification number.
-
C.
hasListingVenue
Indicates that an item, event, or offering is associated with the specific venue where it is listed or made available.
-
D.
isListed
Indicates that an entity appears on or is included in a specified list, registry, or catalog.
-
E.
isListing
Indicates that an entity functions as a listing, typically representing an item, service, or offering that is being presented, advertised, or made available.
- F. None of above. chosen
Provenance (4 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
| PDg | Predicate description generation | batch_69fd509cdc5c8190a5f2c451bc0d0b25 |
completed | May 8, 2026, 2:55 a.m. |
Created at: April 29, 2026, 8:54 p.m.