Triple
T32774972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reply-To |
E838173
|
entity |
| Predicate | isTextualField |
P158893
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Reply-To, isTextualField, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTextualField Context triple: [Reply-To, isTextualField, true]
-
A.
hasTextualCharacter
Indicates that something possesses or exhibits the qualities of written or printed text, such as letters, symbols, or characters.
-
B.
isSimpleField
chosen
Indicates that a field is a basic, non-composite attribute that does not contain or reference nested or complex structures.
-
C.
hasTextualBase
Indicates that one entity serves as the underlying textual source or foundation upon which another entity is based or derived.
-
D.
hasKeyTextType
Indicates that something is associated with a primary or defining type of textual content used as its key or main text.
-
E.
hasTypeOfTextSetting
Indicates that an entity is associated with a particular configuration or style that determines how its text is presented or formatted.
- 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.