Triple
T6625030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M-o-n-t-g-o-m-e-r-y |
E149775
|
entity |
| Predicate | hasComponentLetters |
P54050
|
FINISHED |
| Object | M |
—
|
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: M | Statement: [M-o-n-t-g-o-m-e-r-y, hasComponentLetters, M]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentLetters Context triple: [M-o-n-t-g-o-m-e-r-y, hasComponentLetters, M]
-
A.
hasLetter
Indicates that one entity contains, includes, or is associated with a specific letter or character.
-
B.
hasCodeLetters
Indicates that an entity is associated with, or represented by, a specific sequence of letters used as its code or identifier.
-
C.
hasComponentCharacter
chosen
Indicates that one entity includes another entity as a constituent character or symbolic component.
-
D.
hasAdditionalLetters
Indicates that one entity contains extra or more letters than another entity, beyond a specified base set or reference.
-
E.
hasLetterBy
Indicates that an entity possesses or is associated with a letter authored or sent by another entity.
- 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_69c687ee50048190aa151765bef16193 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6bdb88cc881908f35648c15a7dc85 |
completed | March 27, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69c6ad007c1c8190af425f51011c7ad1 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:58 p.m.