Triple
T14203971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serbian Athens |
E352035
|
entity |
| Predicate | comparisonReason |
P113196
|
FINISHED |
| Object | center of learning |
—
|
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: center of learning | Statement: [Serbian Athens, comparisonReason, center of learning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparisonReason Context triple: [Serbian Athens, comparisonReason, center of learning]
-
A.
comparisonType
Indicates the specific kind of comparison being made between two or more values or entities (e.g., equality, inequality, ordering, or similarity).
-
B.
comparisonProperty
Indicates that one entity is being compared to another based on a specific shared property or attribute.
-
C.
comparisonLevel
Indicates the degree or intensity to which two or more entities are being compared within a given context.
-
D.
comparisonResult
Indicates the outcome of comparing two entities, typically expressing whether one is less than, equal to, or greater than the other.
-
E.
comparisonAspect
Indicates that two or more entities are being compared specifically with respect to a particular shared attribute or dimension.
- 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_69d827894ac0819097803e57f3227b23 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61f6d4d481909128084e82e6a58a |
completed | April 14, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69de05bcd7d48190a4848d9320404aa6 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:05 a.m.