Triple
T28188849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HPFS |
E716246
|
entity |
| Predicate | fileNameCase |
P164109
|
FINISHED |
| Object | case-preserving |
—
|
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: case-preserving | Statement: [HPFS, fileNameCase, case-preserving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fileNameCase Context triple: [HPFS, fileNameCase, case-preserving]
-
A.
letterCase
Indicates the relationship between a character or string and its typographical case (such as uppercase, lowercase, or mixed case).
-
B.
fileName
Indicates the name assigned to a file, typically used to identify or reference that file within a system or context.
-
C.
caseNameVariant
Indicates that one case name is an alternative or variant form of another case name.
-
D.
centralToCase
Indicates that something plays a pivotal or essential role in determining the outcome or understanding of a particular case.
-
E.
typicalCaseCaptionFormat
Indicates the standard or commonly used way of formatting the caption (title block) of a legal case or similar proceeding.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64288631881909ffef7aa84199ae8 |
completed | May 2, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 10:24 p.m.