Triple
T12474174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sydney Futures Exchange |
E298133
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | SFE |
E985564
|
NE 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: SFE | Statement: [Sydney Futures Exchange, hasAbbreviation, SFE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SFE Context triple: [Sydney Futures Exchange, hasAbbreviation, SFE]
-
A.
SFE
chosen
SFE is the abbreviation for the Sydney Futures Exchange, a former Australian financial futures and derivatives exchange that played a key role in the country’s capital markets.
-
B.
SFR
SFR is a major French telecommunications company providing mobile, internet, and television services.
-
C.
SFS
SFS is a renowned Georgetown University school specializing in international affairs, diplomacy, and global policy education.
-
D.
SFS
SFS is a spatial feature standard that defines how geographic features and their properties are modeled and accessed in geospatial information systems.
-
E.
SFS
SFS is a common abbreviation for Allianz Stadium, a major sports and entertainment venue in Sydney, Australia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94dcb194c81908b5e0320ddfd463c |
completed | April 10, 2026, 7:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f64ba3983c8190aef5e3b6a6d2e41e |
completed | May 2, 2026, 7:08 p.m. |
Created at: April 8, 2026, 9:56 p.m.