Triple
T37582531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chung King |
E935009
|
entity |
| Predicate | hasAnchors |
P61394
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Chung King, hasAnchors, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnchors Context triple: [Chung King, hasAnchors, yes]
-
A.
hasAnchorMap
Indicates that there exists a mapping or association between anchors (reference points or anchor elements) and corresponding targets or values.
-
B.
hasPrimaryAnchor
Indicates that one entity serves as the main or principal anchor or reference point for another entity.
-
C.
hasAnchorLocation
Indicates that one entity serves as the fixed reference or attachment point (anchor) for the location or position of another entity.
-
D.
hasAnchorStores
chosen
Indicates that a retail property or shopping center includes one or more major anchor stores as primary tenants.
-
E.
hasAnchorageType
Indicates the specific type or category of anchorage associated with an 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: May 3, 2026, 4:17 p.m.