Triple
T23904064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linkoln |
E601135
|
entity |
| Predicate | modernStandardForm |
P97846
|
FINISHED |
| Object | Lincoln |
—
|
NE NERFINISHED |
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: Lincoln | Statement: [Linkoln, modernStandardForm, Lincoln]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernStandardForm Context triple: [Linkoln, modernStandardForm, Lincoln]
-
A.
standardModernForm
Indicates that an entity is expressed or represented in the currently accepted standard modern form of a language, notation, or system.
-
B.
modernNameForm
chosen
Indicates that one entity is the contemporary or currently used name form corresponding to another entity’s name.
-
C.
standardFormulation
Indicates that something is expressed or represented in a conventional, officially accepted, or commonly used form or version.
-
D.
modernFormSince
Indicates that an entity has existed in its current or modern form starting from a specified point in time.
-
E.
standardFormUsedIn
Indicates that a particular standard form is employed or applied within a given context, process, or system.
- 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cde0674c8190a5e1ce0315ae83cd |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:26 p.m.