Triple
T10170931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoklo language |
E235328
|
entity |
| Predicate | usesRomanizationSystem |
P23170
|
FINISHED |
| Object | TLPA |
E846023
|
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: TLPA | Statement: [Hoklo language, usesRomanizationSystem, TLPA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TLPA Context triple: [Hoklo language, usesRomanizationSystem, TLPA]
-
A.
TLPA
chosen
TLPA is a romanization system used to represent the sounds of the Xiamen (Amoy) dialect of Southern Min Chinese using the Latin alphabet.
-
B.
TLA
TLA is a formal specification language developed by Leslie Lamport for describing and reasoning about concurrent and distributed systems using temporal logic.
-
C.
TPA
TPA is an abbreviation commonly used for a Tri-Party Agreement, a legal contract involving three separate parties that defines their respective rights and obligations.
-
D.
TPA
TPA is the three-letter IATA airport code for Tampa International Airport, a major commercial airport serving the Tampa Bay area in Florida, USA.
-
E.
LEPA
LEPA is the ICAO airport code for Palma de Mallorca Airport, a major international airport in Spain’s Balearic Islands.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec9d36608190be78665cc3410cf2 |
completed | April 2, 2026, 4:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d3177ddab48190988c280faf406383 |
completed | April 6, 2026, 2:16 a.m. |
Created at: March 30, 2026, 9:10 p.m.