Triple
T27113602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 马思纯 |
E686779
|
entity |
| Predicate | 因角色知名 |
P140036
|
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.
knownPrimarilyThrough
Indicates that one entity is chiefly recognized, identified, or made familiar to others by means of another entity (such as a work, role, medium, or context).
-
B.
namedForKnownFor
Indicates that one entity is named after another entity specifically because that other entity is notable or recognized for something.
-
C.
knownForRoleIn
chosen
Indicates that an entity is recognized or notable for performing a particular role in a specific work, project, or context.
-
D.
refersToPersonKnownFor
Indicates that one entity makes reference to a person who is notable or recognized for some specific role, achievement, or characteristic.
-
E.
nowKnownFor
Indicates that an entity is currently recognized or notable for a particular role, attribute, achievement, or association.
- 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_69ef148accd48190b6ed6e13a15f2a4f |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6240450088190af486dbde3daeacb |
completed | May 2, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:55 a.m.