Triple
T34720111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mei Foo Sun Chuen |
E1000889
|
entity |
| Predicate | hasEstateManagementOffice |
P19057
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mei Foo Sun Chuen, hasEstateManagementOffice, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEstateManagementOffice Context triple: [Mei Foo Sun Chuen, hasEstateManagementOffice, true]
-
A.
hasEstateManager
Indicates that an entity is responsible for managing, overseeing, or administering the estate or property of another entity.
-
B.
hasLandOffice
Indicates that an entity maintains or is associated with an official office responsible for managing land-related records, transactions, or administration.
-
C.
hasAssociatedEstate
Indicates that one entity is linked to, or has responsibility for, a particular estate or property.
-
D.
hasAssociatedOffice
chosen
Indicates that an entity is linked to or connected with a particular office in an official or functional capacity.
-
E.
establishedOffice
Indicates that an entity created or set up an official office or place of operation.
- 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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.