Triple
T20530450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M70 |
E504052
|
entity |
| Predicate | similarObjects |
P98121
|
FINISHED |
| Object | M69 |
—
|
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: M69 | Statement: [M70, similarObjects, M69]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: similarObjects Context triple: [M70, similarObjects, M69]
-
A.
similarItemGroup
chosen
Indicates that two or more items belong to the same group because they share similar characteristics, attributes, or functions.
-
B.
moreSimilarTo
Indicates that one entity bears a greater degree of similarity to a second entity than to a third entity, according to some defined similarity measure.
-
C.
similarSchemeIn
Indicates that one entity uses a scheme or structural pattern that is similar to that used in another entity.
-
D.
lessSimilarTo
Indicates that one entity is considered to share fewer similarities or a weaker resemblance with another entity compared to some reference or alternative.
-
E.
materiallySimilarTo
Indicates that two entities share substantially the same physical or material characteristics, composition, or properties, though they may not be exactly identical.
- 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_69e0b4b3a6e08190ae663701f50fab8e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a069edf88190835a9c392c990c55 |
completed | April 20, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:37 a.m.