Triple
T18724423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GPT |
E457859
|
entity |
| Predicate | hasVersion |
P455
|
FINISHED |
| Object | GPT-3.5 |
—
|
NE NERFINISHED |
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: GPT-3.5 | Statement: [GPT, hasVersion, GPT-3.5]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GPT-3.5 Context triple: [GPT, hasVersion, GPT-3.5]
-
A.
GPT-3.5
chosen
GPT-3.5 is a large language model that generates human-like text and powers conversational AI applications such as advanced chatbots and coding assistants.
-
B.
GPT-3
GPT-3 is a large-scale autoregressive language model known for generating human-like text and performing a wide range of natural language tasks with minimal fine-tuning.
-
C.
GPT
GPT is a family of large language models developed by OpenAI that can understand and generate human-like text for a wide range of tasks.
-
D.
GPT
GPT (GUID Partition Table) is a modern disk partitioning scheme that supports large drives, many partitions, and improved reliability compared to older MBR- and APM-based systems.
-
E.
GPT
GPT is the IATA airport code for Gulfport–Biloxi International Airport in Gulfport, Mississippi, United States.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56d72d2c4819080b0d31860976b5e |
completed | April 20, 2026, 12:04 a.m. |
Created at: April 10, 2026, 11:50 a.m.