Triple
T27663137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAA |
E697169
|
entity |
| Predicate | recordTypeCode |
P176293
|
FINISHED |
| Object | 257 |
—
|
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: 257 | Statement: [CAA, recordTypeCode, 257]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordTypeCode Context triple: [CAA, recordTypeCode, 257]
-
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.
recordHolderType
Indicates the role or category that an entity holds in relation to a particular record (e.g., individual, team, organization) within a given context.
-
C.
recordIdentification
Indicates that an entity assigns or maintains a unique identifier or set of identifying information for a specific record.
-
D.
recordStructure
Indicates a relationship where an entity defines, organizes, or specifies the internal layout and components of a record or data structure.
-
E.
recordDetail
Indicates that one entity stores or documents specific information or attributes about another entity.
- F. None of above. chosen
Provenance (4 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6dfcafd0c81908d86662948c539d6 |
completed | May 3, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6df418f488190a5e7ff41f32dceda |
completed | May 3, 2026, 5:38 a.m. |
Created at: April 27, 2026, 2:37 p.m.