Triple
T11749195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Number 1A, 1948 |
E279361
|
entity |
| Predicate | titleFormat |
P81918
|
FINISHED |
| Object | numbered title |
—
|
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: numbered title | Statement: [Number 1A, 1948, titleFormat, numbered title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleFormat Context triple: [Number 1A, 1948, titleFormat, numbered title]
-
A.
titlePattern
Indicates that there is a specific structural or textual pattern that the title of an entity is expected to follow.
-
B.
titleVariant
Indicates that one title is an alternative or variant form of another title referring to the same work or entity.
-
C.
titleType
Indicates the specific category or kind of title associated with an entity (e.g., whether it is a main title, alternative title, working title, etc.).
-
D.
titleHolderStyle
Indicates the manner or format in which a title holder’s status or designation is presented or styled in relation to another entity.
-
E.
titleStylization
chosen
Indicates how the written form of a title is stylistically presented, such as through capitalization, spacing, punctuation, or special formatting.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a508b0c4819082fbcc27d559ea2f |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.