Triple
T11897542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LOA |
E283072
|
entity |
| Predicate | hasStandardFormat |
P32622
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [LOA, hasStandardFormat, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandardFormat Context triple: [LOA, hasStandardFormat, yes]
-
A.
isStandard
chosen
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
-
B.
hasNonStandardForm
Indicates that an entity possesses a form, variant, or representation that deviates from the standard, canonical, or commonly accepted form.
-
C.
hasWorkingFormat
Indicates that one entity possesses or is associated with a functional or operational format of another entity.
-
D.
fileFormatStandard
Indicates that something conforms to, specifies, or defines a standardized structure and rules for how data is organized and stored in a file.
-
E.
hasFormatCurrent
Indicates that an entity is available or expressed in the currently used or most up-to-date format.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8dd13cc10819089d8d5103e562924 |
completed | April 10, 2026, 11:20 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.