Triple
T37845032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahad MIDC industrial area |
E943577
|
entity |
| Predicate | abbreviationOfDeveloper |
P36183
|
FINISHED |
| Object | MIDC |
—
|
NE NERFINISHED |
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: MIDC | Statement: [Mahad MIDC industrial area, abbreviationOfDeveloper, MIDC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abbreviationOfDeveloper Context triple: [Mahad MIDC industrial area, abbreviationOfDeveloper, MIDC]
-
A.
developerAbbreviation
Indicates that one entity is an abbreviation or shortened form used by developers to refer to another entity.
-
B.
developerAcronym
Indicates that an acronym is used as a shortened or abbreviated form of a developer-related term, title, or concept.
-
C.
abbreviationOfMaintainer
Indicates that one identifier or name is an abbreviation or shortened form of the maintainer’s full designation.
-
D.
abbreviationUsedBy
Indicates that a particular abbreviation is employed or adopted by a specified entity in its communication, documentation, or usage.
-
E.
abbreviationUsedFor
chosen
Indicates that a particular shortened form or acronym is used to represent or stand in for a longer term, name, or expression.
- 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.