Triple
T32115976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monster.com Park |
E820238
|
entity |
| Predicate | incorrectInformalUsageOfName |
P174131
|
FINISHED |
| Object | Monster.com Park |
—
|
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: Monster.com Park | Statement: [Monster.com Park, incorrectInformalUsageOfName, Monster.com Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incorrectInformalUsageOfName Context triple: [Monster.com Park, incorrectInformalUsageOfName, Monster.com Park]
-
A.
usesNameDueTo
Indicates that one entity adopts or applies a particular name for another entity specifically because of some motivating reason, circumstance, or dependency.
-
B.
nameUsedIn
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
-
C.
nameUsedBy
Indicates that a particular name is employed or referenced by a specific entity.
-
D.
usesLegalNameOf
Indicates that one entity refers to or identifies another entity by that other entity’s official legal name.
-
E.
nameUsedFor
Indicates that a particular name is used to refer to or designate a given entity.
- F. None of above. chosen
Provenance (4 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: May 1, 2026, 12:28 a.m.