Triple
T37460558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mad Scientist |
E930905
|
entity |
| Predicate | originalFormatStandard |
P84868
|
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: [Mad Scientist, originalFormatStandard, True]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalFormatStandard Context triple: [Mad Scientist, originalFormatStandard, True]
-
A.
fileFormatStandard
chosen
Indicates that something conforms to, specifies, or defines a standardized structure and rules for how data is organized and stored in a file.
-
B.
usedFormat
Indicates that one entity employs or applies a particular format or representation in relation to another entity.
-
C.
originalForm
Indicates that one entity is the earlier, source, or initial version from which another entity is derived or transformed.
-
D.
standardizedFormOf
Indicates that one entity is the normalized or officially standardized version of another, often consolidating variations or alternative forms into a single canonical form.
-
E.
standardFormulation
Indicates that something is expressed or represented in a conventional, officially accepted, or commonly used form or version.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.