Triple
T9002617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iFCP |
E215071
|
entity |
| Predicate | competesWith |
P1375
|
FINISHED |
| Object | FCIP |
E215070
|
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: FCIP | Statement: [iFCP, competesWith, FCIP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FCIP Context triple: [iFCP, competesWith, FCIP]
-
A.
FCIP
chosen
FCIP (Fibre Channel over IP) is a networking protocol that encapsulates Fibre Channel frames within IP networks to enable long-distance connectivity between storage area networks.
-
B.
FIPC
FIPC is a key policymaking body within the Bank of Thailand responsible for formulating and overseeing policies related to financial institutions and the stability of the financial system.
-
C.
FC-FS
FC-FS is a core Fibre Channel standards specification that defines the fundamental framing and signaling mechanisms used for data transport in Fibre Channel networks.
-
D.
iFCP
iFCP is an Internet protocol that enables Fibre Channel storage traffic to be transported over IP networks, facilitating long-distance and wide-area storage networking.
-
E.
FICON
FICON is IBM’s high-speed, Fibre Channel–based input/output interface standard used primarily to connect mainframe computers to storage and peripheral devices.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6957bd5481908ce74f32f8d197de |
completed | April 1, 2026, 12:39 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfdb9741dc8190bec985da8913937c |
completed | April 3, 2026, 3:24 p.m. |
Created at: March 30, 2026, 7:05 p.m.