Triple
T18878171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alice |
E461743
|
entity |
| Predicate | appearsInNotation |
P133304
|
FINISHED |
| Object | A |
—
|
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: A | Statement: [Alice, appearsInNotation, A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInNotation Context triple: [Alice, appearsInNotation, A]
-
A.
typicalNotation
Indicates that one entity is the standard or commonly used symbolic representation (notation) for another entity.
-
B.
distinguishingNotation
Indicates that one entity uses a specific notation or symbol to distinguish or differentiate another entity from similar ones.
-
C.
usesNotationFor
Indicates that one entity employs or adopts a particular notation system or symbolic representation for another entity.
-
D.
hasAlternativeNotation
Indicates that an entity can be represented or written in a different, equivalent form or notation.
-
E.
usesTextInScore
Indicates that one entity incorporates or references a specific text within its score or scoring process.
- F. None of above. chosen
Provenance (4 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c3cfc4408190a7ae91459f75be52 |
completed | April 20, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69e48d22dde8819093b1d963bd673365 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e4978813d081908eaf25bb727fc6cf |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:57 a.m.