Triple
T21513225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U3 |
E530778
|
entity |
| Predicate | hasPlatformProfile |
P9523
|
FINISHED |
| Object | small-profile |
—
|
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: small-profile | Statement: [U3, hasPlatformProfile, small-profile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlatformProfile Context triple: [U3, hasPlatformProfile, small-profile]
-
A.
hasProfile
chosen
Indicates that an entity is associated with or possesses a specific profile representation or account.
-
B.
hasPlatformType
Indicates that an entity is associated with or characterized by a specific type or category of platform.
-
C.
hasDeepPlatform
Indicates that one entity possesses or provides a platform characterized by significant depth, capability, or extensiveness in supporting another entity’s activities or functions.
-
D.
hasPlatformNumber
Indicates that a location or service is associated with a specific platform identified by a platform number.
-
E.
hasPlatformContext
Indicates that something exists or operates within a specific platform environment, configuration, or contextual setting.
- 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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea88e6fc8190a4b73b8d32dae5a8 |
completed | April 23, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:25 p.m.