Triple
T23282516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yin Ruijuan |
E588903
|
entity |
| Predicate | isFollowedOnPlatformService |
P96884
|
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: [Yin Ruijuan, isFollowedOnPlatformService, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFollowedOnPlatformService Context triple: [Yin Ruijuan, isFollowedOnPlatformService, true]
-
A.
followsPlatformOf
chosen
Indicates that one entity subscribes to, tracks, or receives updates from another entity’s activity on a specific platform.
-
B.
followsApproximately
Indicates that one entity follows another in sequence or order, but with some allowable deviation or inexactness in timing, position, or pattern.
-
C.
isFollowedInCalendarBy
Indicates that one event or time period occurs immediately after another in a calendar sequence.
-
D.
relatedPlatformFunction
Indicates that one platform function is associated with, complements, or is otherwise functionally connected to another platform function.
-
E.
followedEarlier
Indicates that one entity began following or tracking another entity at an earlier point in time relative to some reference or comparison.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196447a748190bd797ec9baa63fc3 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:58 p.m.