Triple
T31221053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 万达广场 |
E796009
|
entity |
| Predicate | 开发主体 |
P32488
|
FINISHED |
| Object | 大连万达集团 |
—
|
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: 大连万达集团 | Statement: [万达广场, 开发主体, 大连万达集团]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 开发主体 Context triple: [万达广场, 开发主体, 大连万达集团]
-
A.
developmentLedBy
Indicates that the development of something is directed, managed, or overseen by a particular agent or entity.
-
B.
isDevelopedBy
chosen
Indicates that something (such as a product, project, or idea) is created, produced, or brought into existence through the work or effort of a particular developer or group of developers.
-
C.
developedAs
Indicates that one entity was created, designed, or evolved specifically to function as or replace another entity.
-
D.
majorDeveloper
Indicates that an entity is a primary or leading developer responsible for creating or significantly contributing to another entity.
-
E.
developingAgency
Indicates that one entity serves as the organization or agency responsible for developing or creating 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c4d35848190bd5a2dd81851bea3 |
completed | May 3, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:10 p.m.