Triple
T2254210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joseph Greenberg |
E49682
|
entity |
| Predicate | developedMethod |
P73
|
FINISHED |
| Object | mass lexical comparison |
—
|
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: mass lexical comparison | Statement: [Joseph Greenberg, developedMethod, mass lexical comparison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedMethod Context triple: [Joseph Greenberg, developedMethod, mass lexical comparison]
-
A.
developedThrough
Indicates that something came into existence, was created, or was brought to its current form by means of a specified process, method, or developmental pathway.
-
B.
developed
chosen
Indicates that one entity created, designed, or brought another entity into a more advanced or complete state through effort or work.
-
C.
developedAs
Indicates that one entity was created, designed, or evolved specifically to function as or replace another entity.
-
D.
inspiredDevelopmentOf
Indicates that one entity served as a motivating influence or creative stimulus leading to the development or creation of another entity.
-
E.
developedInCase
Indicates that something (such as a method, argument, or principle) was formulated, articulated, or established within the context of a particular case.
- 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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc12029548190af9f2cdd7a4de2d6 |
completed | March 7, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69abbdb34c148190b51e99f540f97204 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.