Triple
T16897147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minor |
E424334
|
entity |
| Predicate | mayRelateTo |
P125111
|
FINISHED |
| Object | Latin word minor |
—
|
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: Latin word minor | Statement: [Minor, mayRelateTo, Latin word minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayRelateTo Context triple: [Minor, mayRelateTo, Latin word minor]
-
A.
moreCloselyRelatedTo
Indicates that one entity has a stronger or closer relationship, connection, or similarity to a second entity than to some other reference entity.
-
B.
mayEntail
Indicates that one statement or condition can logically lead to or imply the truth of another, without guaranteeing it.
-
C.
laterRelationWith
Indicates that one entity stands in a temporal relationship to another such that it occurs or exists at a later time than the other.
-
D.
possibleRelative
Indicates a relationship where one entity may be related to another by family or kinship, but the exact nature of the relationship is uncertain or not fully established.
-
E.
subjectRelation
Indicates that one entity stands in a specified relational role or connection to another entity.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3c8d880208190ad2b2c8616b54ea3 |
completed | April 18, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:29 a.m.