Triple
T7435991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TCDP |
E171615
|
entity |
| Predicate | acronym |
P43
|
FINISHED |
| Object | TCDP |
E171615
|
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: TCDP | Statement: [TCDP, acronym, TCDP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TCDP Context triple: [TCDP, acronym, TCDP]
-
A.
TCDP
chosen
TCDP is a specialized committee within the IEEE Computer Society that focuses on advancing research, standards, and community activities in distributed computing and distributed systems.
-
B.
TCD
TCD is the three-letter ISO 3166-1 alpha-3 country code assigned to Chad.
-
C.
TDXP
TDXP is the stock ticker symbol for the TecDAX index, which tracks major German technology companies listed on the Frankfurt Stock Exchange.
-
D.
CPC
CPC is the commonly used abbreviation for the Communist Party of Canada, a Marxist–Leninist political party in Canada.
-
E.
CPC
CPC is the commonly used abbreviation for the Code of Civil Procedure, 1908, which governs the procedural rules for civil litigation in India.
- 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_69c68a64228c8190affaec2a8127ce7b |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f347f25081908e6086d4073295f5 |
completed | March 27, 2026, 9:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c81f228014819088220b2cefc3ee41 |
completed | March 28, 2026, 6:34 p.m. |
Created at: March 27, 2026, 3:13 p.m.