Triple
T18771300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M43 |
E459021
|
entity |
| Predicate | hasPhysicalAssociationWith |
P69912
|
FINISHED |
| Object | M42 |
—
|
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: M42 | Statement: [M43, hasPhysicalAssociationWith, M42]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhysicalAssociationWith Context triple: [M43, hasPhysicalAssociationWith, M42]
-
A.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
B.
companionPhysicalAssociation
chosen
Indicates a relationship where one entity is physically accompanying or co-located with another as a companion.
-
C.
elementalAssociation
Indicates an association where one entity is linked or related to a particular element or elemental property (such as fire, water, earth, or air).
-
D.
notablyAssociatedWith
Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
-
E.
associatedWithMaterial
Indicates a relationship where something is linked or connected to a particular material, typically as its substance, component, or relevant physical medium.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e59335a01881908731371be1e27a6b |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.