Triple
T13652988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TCC |
E326784
|
entity |
| Predicate | typicalPublicationType |
P218
|
FINISHED |
| Object | conference proceedings |
—
|
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: conference proceedings | Statement: [TCC, typicalPublicationType, conference proceedings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPublicationType Context triple: [TCC, typicalPublicationType, conference proceedings]
-
A.
publicationType
chosen
Indicates the specific category or format of a published work that characterizes how it is issued or presented.
-
B.
publicationSeriesType
Indicates the specific kind or category of series to which a publication belongs (e.g., journal series, book series, report series).
-
C.
journalType
Indicates the specific category or format of a journal associated with an entity.
-
D.
officialPublication
Indicates that an entity is an authoritative, formally released publication issued by an official or governing body.
-
E.
publicationBody
Indicates the organization or entity that serves as the publishing body responsible for issuing the referenced work.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc609676c8190b5b1cabe6b315142 |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:52 p.m.