Triple
T32774985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reply-To |
E838173
|
entity |
| Predicate | isInsertedIn |
P135551
|
FINISHED |
| Object | message header section |
—
|
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: message header section | Statement: [Reply-To, isInsertedIn, message header section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInsertedIn Context triple: [Reply-To, isInsertedIn, message header section]
-
A.
isReferencedIn
Indicates that one entity is cited, mentioned, or otherwise referred to within another entity.
-
B.
hasPutIn
chosen
Indicates that one entity has placed or inserted another entity into a container, location, or context.
-
C.
isAt
Indicates that one entity is located at or present in the place or position of another entity.
-
D.
isTargetIn
Indicates that a specified entity lies within, or is contained inside, a given target region, set, or scope.
-
E.
isInUse
Indicates that an entity is currently being utilized or actively engaged in its intended function or operation.
- 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:13 a.m.