Triple
T8906466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 外滩 |
E212071
|
entity |
| Predicate | 面向人群 |
P10804
|
FINISHED |
| Object | 国内游客 |
—
|
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: 国内游客 | Statement: [外滩, 面向人群, 国内游客]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 面向人群 Context triple: [外滩, 面向人群, 国内游客]
-
A.
面向对象层次
Indicates a hierarchical relationship in object-oriented design, where entities are organized into layered or ranked levels based on inheritance, abstraction, or responsibility.
-
B.
suitableForLargeGroups
Indicates that something can comfortably accommodate or is appropriate for use by a relatively high number of people at the same time.
-
C.
peopleGroupOf
Indicates that one entity is a group or collection composed of the people represented by the other entity.
-
D.
typicalAudience
chosen
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
E.
relatesToAudience
Indicates a general relationship or relevance between something and a particular audience or group of recipients.
- 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_69ca839255248190b43984294abd92ae |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc64c51d6c819098dc33a480dfd462 |
completed | April 1, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:55 p.m.