Triple
T33652067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Securities and Futures Ordinance |
E862124
|
entity |
| Predicate | ordinanceNumber |
P1117
|
FINISHED |
| Object | Cap. 571 |
—
|
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: Cap. 571 | Statement: [Securities and Futures Ordinance, ordinanceNumber, Cap. 571]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordinanceNumber Context triple: [Securities and Futures Ordinance, ordinanceNumber, Cap. 571]
-
A.
recognizedAsOrdinanceBy
Indicates that something is formally acknowledged or accepted as an ordinance by a particular authority or governing body.
-
B.
requiresOrdinance
Indicates that one entity can only be established, changed, or carried out if a formal ordinance is enacted or in place.
-
C.
mayoralOrder
Indicates an official directive or decision issued by a mayor to be carried out by others.
-
D.
publicLawNumber
chosen
Indicates the specific public law identifier associated with a legislative act or statute.
-
E.
legislatureNumber
Indicates the specific numbered session or term of a legislative body associated with an entity or event.
- 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_69f349840ba881908e3bfce536aeb92b |
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:42 a.m.