Triple
T32774958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reply-To |
E838173
|
entity |
| Predicate | fieldSyntax |
P179854
|
FINISHED |
| Object | mailbox-list |
—
|
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: mailbox-list | Statement: [Reply-To, fieldSyntax, mailbox-list]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldSyntax Context triple: [Reply-To, fieldSyntax, mailbox-list]
-
A.
fieldPattern
Indicates a recurring or structured arrangement or configuration present within a field or area.
-
B.
fieldComposition
Indicates how the components or elements within a field are organized, combined, or structured in relation to one another.
-
C.
fieldComponent
Indicates that one entity functions as a constituent or sub-part within a larger field or domain defined by another entity.
-
D.
fieldName
Indicates the specific name or label assigned to a field within a data structure, form, or record.
-
E.
fieldStrategy
Indicates a strategic approach or plan applied within a particular field, domain, or area of activity.
- 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_69f727ad9ff88190ba8069dd48b2e98f |
completed | May 3, 2026, 10:47 a.m. |
Created at: May 1, 2026, 1:13 a.m.