Triple
T12515275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-record |
E299177
|
entity |
| Predicate | recordTypePrefix |
P91206
|
FINISHED |
| Object | S |
—
|
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: S | Statement: [S-record, recordTypePrefix, S]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordTypePrefix Context triple: [S-record, recordTypePrefix, S]
-
A.
recordsType
Indicates that one entity documents, stores, or keeps an official account of a particular type or category of information, event, or item.
-
B.
registrationPrefix
Indicates that an entity has a specific registration prefix code assigned to it as part of its official registration or identification.
-
C.
namePrefix
Indicates that one entity is a prefix or leading part of another entity’s name.
-
D.
recordStructure
Indicates a relationship where an entity defines, organizes, or specifies the internal layout and components of a record or data structure.
-
E.
recordClass
chosen
Indicates that one entity is classified or categorized as a particular type or class within a record or recording system.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.